Re: Do I have to release the patch for a GPL software under GPL?

2006-05-15 Thread Gordon Burditt
Now, I, Evil Bill Fence Door, copyright this patch, sell it with onerous copy protection, and for $1,000,000 a copy. The license that comes with it prohibits re-distribution of the patch. Note that I'm *not* re-distributing any GPL-licensed software. But you _modified_ a GPL

Re: Do I have to release the patch for a GPL software under GPL?

2006-05-15 Thread Alexander Terekhov
Merijn de Weerd wrote: On 2006-05-13, Alexander Terekhov [EMAIL PROTECTED] wrote: Merijn de Weerd wrote: My reply is an original work of authorship. I provided annotations and other modifications to the message I replied to. Therefore my reply is and only can be a derivative work.

Re: Do I have to release the patch for a GPL software under GPL?

2006-05-15 Thread Alexander Terekhov
Gordon Burditt wrote: Now, I, Evil Bill Fence Door, copyright this patch, sell it with onerous copy protection, and for $1,000,000 a copy. The license that comes with it prohibits re-distribution of the patch. Note that I'm *not* re-distributing any GPL-licensed software.

DLL Copyright

2006-05-15 Thread Jacob JKW
Hi all, The following happens: 1) Source code to an executable is released under the GPL by author #1. 2) Source code is lightly modified by author #2 and then included as a DLL bundled with a new GPL app by a author #2. How should the copyright info be handled? Many thanks, J.

Re: DLL Copyright

2006-05-15 Thread Alexander Terekhov
Jacob JKW wrote: Hi all, The following happens: 1) Source code to an executable is released under the GPL by author #1. 2) Source code is lightly modified by author #2 and then included as a DLL bundled with a new GPL app by a author #2. How should the copyright info be handled?

Re: DLL Copyright

2006-05-15 Thread Alfred M. Szmidt
The following happens: 1) Source code to an executable is released under the GPL by author #1. 2) Source code is lightly modified by author #2 and then included as a DLL bundled with a new GPL app by a author #2. How should the copyright info be handled? The DLL bundle must be

Re: GPL and inhouse use?

2006-05-15 Thread Eric
Merijn de Weerd wrote: On 2006-05-14, Eric [EMAIL PROTECTED] wrote: Well, suppose, hypothetically, that you added a lot of code to the kernel/base distribution, stripped out some of the base distribution stuff (like X or whaever) too in order to create a really robust and unique testing

Re: GPL and inhouse use?

2006-05-15 Thread John Hasler
Eric writes: so its basically if i modify any gpl'd code I must give away my changes whether or not i keep it 'in-house' ? No. Wow, if i have that right... You don't. If you do not distribute your modified GPLd code you are not required to show the source to anyone. Read the GPL. It's