On Nov 04, 2008 at 15:58, Ondrej Martinek <[EMAIL PROTECTED]> wrote: [...] > >> > >> Andrei: I quite sure you can't add new stuff under BSD (or any other > >> license) to GPL-ed original without the result not ending up as GPL. > > > > IANAL, but what makes you believe so? > > By adding new stuff, modifying the original you create a derivative > work. In example, see > http://en.wikipedia.org/wiki/GNU_General_Public_License, section "The > GPL in court" states: > > "The GPL is clear in requiring that all derivative works of code > under the GPL must themselves be under the GPL."
Yes, the derivative work of code under GPL must be GPL, but: - this doesn't meant that I cannot add a differently licensed file to a GPL project, as long as the license is GPL _compatible_. The project as a whole will be GPL, but the respective file in particular will not. - this doesn't meant I can't have patches to GPL files and the patches themselves under some GPL compatible license. In this case the file will still be under GPL, but the code added by the patches will not (e.g. for a BSD patch, one could take only the code from the patch and use it in another non-GPL project). So the project as a whole will be GPL, but that doesn't mean that I can't have parts of it licensed with a different but GPL compatible license, as long as I follow the terms of the GPL when distributing. Example: the linux kernel is GPL, but contains BSD licensed files (e.g. drivers/net/ppp_deflate.c ). Note: by BSD I mean the modified BSD license (original BSD without the advertising clause). For more info see: http://www.gnu.org/licenses/gpl-faq.html#WhatDoesCompatMean http://www.gnu.org/philosophy/license-list.html#GPLCompatibleLicenses http://www.gnu.org/copyleft/gpl-faq.html#GPLAndPlugins http://www.softwarefreedom.org/resources/2007/gpl-non-gpl-collaboration.html Andrei _______________________________________________ Serdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/serdev
