Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] barebox: fix license information
Date: Wed, 22 Aug 2012 22:18:47 +0200	[thread overview]
Message-ID: <50353EA7.6030901@lucaceresoli.net> (raw)
In-Reply-To: <20120822194924.268ac192@skate>

Thomas Petazzoni wrote:
> Le Wed, 22 Aug 2012 13:47:33 +0100,
> spdawson at gmail.com a ?crit :
>
>> From: Simon Dawson <spdawson@gmail.com>
>>
>> The barebox license is GPLv2, and not GPLv2+.
>>
>> Signed-off-by: Simon Dawson <spdawson@gmail.com>
>
> Thanks, applied.
>
> However, the Barebox license, just like U-Boot license, has a special
> exception to allow proprietary standalone applications to be linked
> against parts of Barebox/U-Boot without having to be released under the
> GPL. Should be use "GPLv2 with exceptions"? Or something else?

Ouch. Well, practically speaking, AFAIK we don't include standalone
Barebox applications in Buildroot, so this a NOOP in our case. If a user
includes such applications in their own copy of Busybox and build it with
Buildroot, then we may kind of assume that user will take care of handling
this case...

But from a formal and "legally-technical" POV, this license has some
exceptions to the original FSF text, so to be safe we should go that way.

I have no strong opinions at this time of the day, but I generally think
that when speaking legal, we should be as safe as possible.
So I'm moderately convinced this is a "GPLv2 with exceptions".

Other opinions are very welcome.

Luca

  reply	other threads:[~2012-08-22 20:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 12:47 [Buildroot] [PATCH] barebox: fix license information spdawson at gmail.com
2012-08-22 17:49 ` Thomas Petazzoni
2012-08-22 20:18   ` Luca Ceresoli [this message]
2012-08-26 22:00     ` Arnout Vandecappelle
2012-08-28  7:17       ` Simon Dawson

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=50353EA7.6030901@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