From: "David Schwartz" <davids@webmaster.com>
To: <linux-kernel@vger.kernel.org>
Cc: <clemens@endorphin.org>
Subject: RE: GPL version, "at your option"?
Date: Wed, 17 Nov 2004 17:04:28 -0800 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKEEOHPNAA.davids@webmaster.com> (raw)
In-Reply-To: <1100614115.16127.16.camel@ghanima>
> As the text says, the licensee can choose the GPL version at his option,
> and he is likely to choose the one with better conditions. So, newer
> version can never limit the licensee's right, because he is always free
> to choose version 2. Therefore, successor versions can only remove
> limitations.
Your logic is totally flawed. Successor versions can certainly add
limitations.
Consider the following hypothetical, GPL version 3 allows you to relicense
the code under the FreeBSD license. Someone relicenses Linux (with lots of
later modification) under the FreeBSD license. Now people who receive the
binaries from this new stream of Linux are not entitled to the source code.
Not that this would ever happen, of course, but if your question is, "what
possible harm could it do", the answer is that new limitations could be put
in the newer licenses and newer code could be released with only the new
license.
When Linux opted to apply the GPL to early versions of Linux, he wasn't
concerned only with protecting that code as it existed at that instant. He
was creating the framework that shapes the future development of Linux into
the future. The "at your option" clause could be used to transfer that
contorl to the FSF.
Suppose GPL version 3 has no requirement that you make the source
available. I can then ship Linux without making any source available at all
by claiming that I'm using that later version at my option.
DS
next prev parent reply other threads:[~2004-11-18 1:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 14:08 Fruhwirth Clemens
2004-11-16 14:35 ` Erik Mouw
2004-11-16 14:58 ` Fruhwirth Clemens
2004-11-16 14:40 ` Charles Cazabon
2004-11-17 15:07 ` Alan Cox
2004-11-17 16:33 ` Michael Poole
2004-11-17 16:09 ` Alan Cox
2004-11-16 14:48 ` Tim Schmielau
2004-11-16 15:46 ` Linus Torvalds
2004-11-17 15:09 ` Alan Cox
2004-11-17 16:28 ` Linus Torvalds
2004-11-17 16:16 ` Alan Cox
2004-11-17 17:59 ` Linus Torvalds
2004-11-17 21:11 ` Jesper Juhl
2004-11-16 15:38 ` James Morris
2004-11-18 1:04 ` David Schwartz [this message]
2004-11-18 2:12 ` Kyle Moffett
2004-11-18 2:50 ` Dmitry Torokhov
2004-11-18 3:11 ` Kyle Moffett
2004-11-18 4:54 ` Dmitry Torokhov
2004-11-18 15:46 ` David Schwartz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MDEHLPKNGKAHNMBLJOLKEEOHPNAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=clemens@endorphin.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®