Actually, as long as it's the copyright holder, he/she can put it under 
any number of licenses.  So, in releasing the new version, the old GPL'd 
stuff is re-released under the new license, along with any new code.

However, as you say, those versions out there are still under the GPL, and 
can be forked.

Paul Lussier said:
>In a message dated: Wed, 30 May 2001 15:33:08 EDT
>Mark Komarinski said:
>
>>You can "revoke" the GPL and put newer versions under a different 
license.
>>
>>Best example of this is the OGG Vorbis group, which went from a GPL
>>license to a BSD license (with RMS's grudging blessing).  This
>>was to allow hardware vendors to quickly add OGG support in hardware
>>without thinking that the GPL was going to trample their IP.
>
>Well, I suppose, but wouldn't a "new" version have to be a complete
>rewrite and not include any code previously released under the GPL?
>If it did include code previously released under the GPL, wouldn't
>the viral nature of the GPL constitute that as a derivative work?
>
>Additionally, say you are allowed to "revoke" the license for future
>versions of the code, that doesn't mean that the versions previously
>released under the GPL are now "revoked" does it?  Those are still
>out there and free, therefore, anyone can take that code and perpetuate
>it with modifications, right?
>-- 

jeff

-----------------------------------------------------------------------
Jeffry Smith      Technical Sales Consultant     Mission Critical Linux
[EMAIL PROTECTED]   phone:603.930.9739 fax:978.446.9470
-----------------------------------------------------------------------
Thought for today:  Guido /gwee'do/ or /khwee'do/ 

  Without qualification,
   Guido van Rossum (author of Python).  Note that Guido answers to
   English /gwee'do/ but in Dutch it's /khwee'do/.





**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************

Reply via email to