From: matz@... (Yukihiro Matsumoto)
Date: 2001-09-24T10:02:42+09:00
Subject: [ruby-talk:21614] Re: Ruby licence in commercial software

Hi,

In message "[ruby-talk:21603] Re: Ruby licence in commercial software"
    on 01/09/24, Scott <accbuy@hotmail.com> writes:

|Having not worked with the LGPL as much as probably others on this
|list; is there check list or site that shows what things they would
|have to do when releasing the commercial software as far as notices
|and readme's?
|
|The reason behind this question is:  What if you feel it makes no
|difference to the user what the program was written in?  You could
|include all the source but never really say correct?   OR is there
|something that has to be shown to the user ?  What have other
|companies done ?

OK, here's the checklist, see README for detail.

  * you have to distribute the ORIGINAL Ruby source code with your
    software.

  * or mention place to fetch the original source (e.g. URL) in the
    documention of your software.

  * you must give new name it if you distribute modified version of
    Ruby.  But you don't have to disclose your modificaion.

  * if you disclose modified source code of Ruby, you have to mention
    that it's modified.

Notice it's not LGPL checklist.  Don't apply this to other LGPL softwares.

							matz.