From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/5] COPYING: add exception about patch licensing
Date: Fri, 19 Feb 2016 18:28:01 +0100 [thread overview]
Message-ID: <56C750A1.5050908@lucaceresoli.net> (raw)
In-Reply-To: <56BBBB2A.1060706@mind.be>
Arnout, All,
On 10/02/2016 23:35, Arnout Vandecappelle wrote:
> On 04-02-16 00:02, Yann E. MORIN wrote:
>> Luca, All,
>>
>> On 2016-02-01 23:19 +0100, Luca Ceresoli spake thusly:
>>>> Several people have been asking what is the license of the patches
>>>> provided by Buildroot. COPYING is the authoritative place to state it.
>>>>
>>>> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
>>>> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>>>> Cc: Arnout Vandecappelle <arnout@mind.be>
>>>> ---
>>>> Changes v1 -> v2:
>>>> - Rewrite it almost entirely (Arnout, Thomas).
>>>> ---
>>>> COPYING | 8 ++++++++
>>>> 1 file changed, 8 insertions(+)
>>>>
>>>> diff --git a/COPYING b/COPYING
>>>> index d511905..3596777 100644
>>>> --- a/COPYING
>>>> +++ b/COPYING
>>>> @@ -1,3 +1,11 @@
>>>> +Except for the patches provided for packages, Buildroot is licensed
>>>> +under the GNU General Public License, version 2.
>> There a gotcha here. The manual states, in chapter 12.3:
>>
>> Buildroot [is] released under the GNU General Public License,
>> version 2 or (at your option) any later version.
>>
>> So, we have to clarify: is it GPLv2 or GPLV2+ ?
>>
>> It's too late today for me to go digging; I'll do that tomorrow. Just
>> rmind me before the end of the week if there's not feedback from my part
>> on this topic.
>
> Reminder :-)
>
> But I did the digging. The situation is of course complicated.
>
> We don't have many files that specify a license by themselves. All of them
> specify 'or later', except for makedevs.c (obviously, because it is copied from
> busybox), toolchain-wrapper.c (added by Peter in 2011), and the manual itself,
> which specify v2 only.
>
> The top-level Makefile is the only thing of which you could say that it has
> project-wide scope. And that says 'or later'.
>
> So, what does that mean for buildroot as a whole? I think it is GPLv2+, except
> for the package patches and except for the files that explicitly specify a
> different license. Can we fit that in the formulation that evolved in this thread?
Here's what I've been able to come up with so far. It's basically:
- the sum of the present thread, plus
- a reduced and modified version of the preamble suggested in the
GNU GPL itself (section "How to Apply These Terms to Your New
Programs"), plus
- the statement that BR is GPLv2+ except where differently stated,
as Arnout suggested.
I'm sure this needs further discussion and improvements.
-------------------------8<----------------------
With the exceptions below, Buildroot is distributed under the terms of
the GNU General Public License, reproduced below; either version 2 of
the License, or (at your option) any later version.
Some files in Buildroot contain a different license statement. Those
files are licensed under the license contained in the file itself.
Buildroot also bundles patch files, which are applied to the sources
of the various packages. Those patches are not covered by the license
of Buildroot. Instead, they are covered by the license of the software
to which the patches are applied. When said software is available
under multiple licenses, the Buildroot patches are only provided under
the publicly accessible licenses.
-------------------------8<----------------------
--
Luca
next prev parent reply other threads:[~2016-02-19 17:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 22:19 [Buildroot] [PATCH v2 0/5] Patch file clarification & Co Luca Ceresoli
2016-02-01 22:19 ` [Buildroot] [PATCH v2 1/5] Update copyright year Luca Ceresoli
2016-02-01 22:24 ` Luca Ceresoli
2016-02-01 22:19 ` [Buildroot] [PATCH v2 2/5] docs/manual: slightly clarify patch licensing Luca Ceresoli
2016-02-02 8:58 ` Yann E. MORIN
2016-02-03 22:53 ` Yann E. MORIN
2016-02-10 22:15 ` Arnout Vandecappelle
2016-02-25 10:50 ` Peter Korsgaard
2016-02-01 22:19 ` [Buildroot] [PATCH v2 3/5] COPYING: add exception about " Luca Ceresoli
2016-02-01 22:31 ` Thomas Petazzoni
2016-02-03 23:02 ` Yann E. MORIN
2016-02-03 23:57 ` Arnout Vandecappelle
2016-02-04 20:42 ` Yann E. MORIN
2016-02-04 21:08 ` Thomas Petazzoni
2016-02-04 21:40 ` Yann E. MORIN
2016-02-04 21:51 ` Thomas Petazzoni
2016-02-04 22:28 ` Steve Calfee
2016-02-05 9:25 ` Luca Ceresoli
2016-02-05 12:07 ` Peter Korsgaard
2016-02-10 22:35 ` Arnout Vandecappelle
2016-02-19 17:28 ` Luca Ceresoli [this message]
2016-02-25 10:57 ` Peter Korsgaard
2016-02-25 11:53 ` Luca Ceresoli
2016-02-01 22:19 ` [Buildroot] [PATCH v2 4/5] docs/manual: add section " Luca Ceresoli
2016-02-03 23:34 ` Yann E. MORIN
2016-02-26 22:08 ` Luca Ceresoli
2016-02-26 22:28 ` Yann E. MORIN
2016-02-10 22:37 ` Arnout Vandecappelle
2016-02-01 22:19 ` [Buildroot] [PATCH v2 5/5] legal-info: explicitly state how patches are licensed Luca Ceresoli
2016-03-06 15:14 ` Thomas Petazzoni
2016-03-06 22:52 ` Luca Ceresoli
2016-03-06 22:56 ` Yann E. MORIN
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=56C750A1.5050908@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