RE: GPLv3 Position Statement
From: David Schwartz
Date: Fri Sep 29 2006 - 03:20:00 EST
> So what would happen if I add an essential GPL2-only file to a "GPL2
> or later" project?
The files would have to act as a license boundary. Otherwise, it would be
GPL2 only. (However, I think people could reasonably assume that if someone
contributed to a GPL2 or later project, they intended their work to be
licensed the same as the project.)
> Let's recall, a proprietary program that
> combines/derives with GPL code makes the final binary GPL (and hence
> the source, etc. and whatnot, don't stretch it). Question: The Linux
> kernel does have GPL2 and GPL2+later combined, what does this make
> the final binary?
GPL2. If you combine dual licensed code with GPLv2 code, the result must be
> (Maybe you implicitly answered it by this already, please indicate):
> >Exactly. The GPLv3 can _only_ take over a GPLv2 project if the
> "or later"
> From that I'd say it remains GPL2 only.
I still don't see how it can take over, unless the FSF fixes the "bug" in
GPLv3. GPLv2 does not permit such takeover, and unless GPLv3 is amended to
do so, such a takeover is prohibited.
I could be in error, I haven't looked closely enough. But if I'm right, I
presume the FSF will be tipped off by someone and fix it. If anyone from the
FSF is listening, you need to add a clause to GPLv3 permitting you to modify
any project licensed under both the GPLv3 and another license such non-GPL
and/or earlier-GPL licenses can be removed. Otherwise, no 'GPLv2 or later'
project can become 'GPLv3 or later'. (Unless that's intentional.)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/