From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v2 16/31] linux: define license
Date: Fri, 09 Mar 2012 17:23:08 +0100 [thread overview]
Message-ID: <4F5A2E6C.9030202@lucaceresoli.net> (raw)
In-Reply-To: <201203072249.40319.yann.morin.1998@free.fr>
Yann E. MORIN wrote:
> Lucas, All,
>
> On Wednesday 07 March 2012 21:58:16 Luca Ceresoli wrote:
>> Signed-off-by: Luca Ceresoli<luca@lucaceresoli.net>
>> ---
>> linux/linux.mk | 2 ++
>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/linux/linux.mk b/linux/linux.mk
>> index ae236d4..e6f2388 100644
>> --- a/linux/linux.mk
>> +++ b/linux/linux.mk
>> @@ -4,6 +4,8 @@
>> #
>> ###############################################################################
>> LINUX_VERSION=$(call qstrip,$(BR2_LINUX_KERNEL_VERSION))
>> +LINUX_LICENSE = GPLv2-ONLY
> What's the point of giving the version 'v2' and stating 'only'?
> I would rather see:
> values meaning
> -------------------------------
> GPLv2 GPLv2 only
> GPLv2+ GPLv2 or later
> LGPLv2.1 LGPLv2.1 only
> LGPLv2.1+ LGPLv2.1 or later
> ... ...
When a project is GPL-licensed, it usually means it uses "either version X of
the License, or (at your option) any later version". There are rare cases
(Linux, Busybox, any other?) chose to use a specific version, no later version.
So the "default" meaning of "GPLvX" is "GPL version X or later". Those rare
cases that allow no upgrade are distinguished by adding "only".
This applies for example to:
- http://en.wikipedia.org/wiki/Linux_kernel
- http://en.wikipedia.org/wiki/Directfb
- http://en.wikipedia.org/wiki/Lzop
I prefer to do the same, and use a concise definition for the most frequent
case. Of course this is a personal preference.
If we wanted to stay on the extra-safe side, we might use:
values meaning
-------------------------------
GPLv2-ONLY GPLv2 only
GPLv2+ GPLv2 or later
LGPLv2.1-ONLY LGPLv2.1 only
LGPLv2.1+ LGPLv2.1 or later
... ...
so there is no ambiguity whatsoever. Might that "+" sign create doubts in
dummies reading it ("Hey, what's GPLv2+? a super-GPLv2?")?
Your opinions?
Luca
next prev parent reply other threads:[~2012-03-09 16:23 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 20:58 [Buildroot] [RFC v2 00/31] Automatically produce legal compliance info Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 01/31] legal-info: infrastructure to collect legally-relevant material Luca Ceresoli
2012-03-09 7:45 ` Thomas De Schampheleire
2012-03-09 8:51 ` Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 02/31] cups: warn that legal-info is not implemented Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 03/31] fis: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 04/31] doom-wad: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 05/31] gettext: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 06/31] microperl: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 07/31] netkitbase: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 08/31] netkittelnet: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 09/31] newt: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 10/31] tinyhttpd: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 11/31] ttcp: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 12/31] uemacs: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 13/31] vpnc: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 14/31] xfsprogs: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 15/31] mpc: define license Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 16/31] linux: " Luca Ceresoli
2012-03-07 21:49 ` Yann E. MORIN
2012-03-09 16:23 ` Luca Ceresoli [this message]
2012-03-09 20:12 ` Thomas De Schampheleire
2012-04-16 21:19 ` Luca Ceresoli
2012-04-16 21:38 ` Yann E. MORIN
2012-04-16 21:40 ` Yann E. MORIN
2012-04-18 14:15 ` Thomas De Schampheleire
2012-04-18 15:39 ` Luca Ceresoli
2012-04-18 15:39 ` Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 17/31] m4: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 18/31] busybox: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 19/31] bzip2: " Luca Ceresoli
2012-03-07 21:52 ` Yann E. MORIN
2012-03-09 16:00 ` Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 20/31] directfb: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 21/31] iostat: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 22/31] lzo: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 23/31] lzop: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 24/31] tslib: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 25/31] libusb: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 26/31] pcre: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 27/31] netsnmp: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 28/31] berkeleydb: " Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 29/31] qt: define license choice Luca Ceresoli
2012-03-10 12:43 ` Arnout Vandecappelle
2012-03-07 20:58 ` [Buildroot] [RFC v2 30/31] foobar: create a fake proprietary package (testing only) Luca Ceresoli
2012-03-07 20:58 ` [Buildroot] [RFC v2 31/31] Create test configs " Luca Ceresoli
2012-03-07 21:30 ` [Buildroot] [RFC v2 00/31] Automatically produce legal compliance info Luca Ceresoli
2012-03-07 21:41 ` Yann E. MORIN
2012-03-08 10:02 ` Luca Ceresoli
2012-03-08 18:46 ` Yann E. MORIN
2012-03-09 8:48 ` Thomas De Schampheleire
2012-03-10 12:46 ` Arnout Vandecappelle
2012-03-07 21:54 ` Yann E. MORIN
2012-03-08 9:14 ` Luca Ceresoli
2012-03-09 8:47 ` Thomas De Schampheleire
2012-03-09 9:12 ` Luca Ceresoli
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=4F5A2E6C.9030202@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--cc=buildroot@busybox.net \
/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