Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/5] COPYING: add exception about patch licensing
Date: Thu, 4 Feb 2016 00:57:38 +0100	[thread overview]
Message-ID: <56B293F2.9070201@mind.be> (raw)
In-Reply-To: <20160203230208.GB3428@free.fr>



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.
> 
> Until then, NAK.
> 
>> +Patches provided by Buildroot for packages are released under the same
>> +license as the software that they modify.
> 
> Here's an alternative proposal, to replace both sentences:
> 
>     Buildroot comes with its own license, reproduced below.
> 
>     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. See those individual packages for
>     their license (running 'make legal-info' after your build may
>     help).

 Much better.

 Still better:

    Buildroot comes with its own license, reproduced below.

    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, but are provided under the same
    license as the software they apply to. Run 'make legal-info' to
    collect the licenses of your selected packages and their patches.

(borrowing from the update of the manual here).

 Note that this sentence doesn't clarify the issue of proprietary licenses. It's
basically still the same as what we have now in that respect.

 Regards,
 Arnout

> 
> Regards,
> Yann E. MORIN.
> 
>> +-----------------------------------------------------------------
>> +
>>  		    GNU GENERAL PUBLIC LICENSE
>>  		       Version 2, June 1991
>>  
>> -- 
>> 1.9.1
>>
> 

-- 
Arnout Vandecappelle      arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2016-02-03 23:57 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 [this message]
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
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=56B293F2.9070201@mind.be \
    --to=arnout@mind.be \
    --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