From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uboot-tools: fix license issues
Date: Thu, 24 Oct 2013 21:29:32 +0200 [thread overview]
Message-ID: <5269751C.1000207@mind.be> (raw)
In-Reply-To: <526913FC.7070905@zacarias.com.ar>
On 24/10/13 14:35, Gustavo Zacarias wrote:
> On 10/24/2013 09:24 AM, Arnout Vandecappelle wrote:
>> Now, for the specific case of U-Boot, we can do better: if _VERSION is
>> 2013.10 or larger, we can use the new license specification, else the
>> old one (and due to U-Boot's versioning policy we can just use sort;
>> custom has to be handled separately anyway).
>
> We don't use version choices any more, just a recommended version
> string, so matching might not be that easy.
We don't? Then what does BR2_TARGET_UBOOT_CUSTOM_VERSION do?
> And there's custom tarball / git repo / etc too.
Exactly, for these the other considerations still apply.
>
>> But another issue is that the license that we specify is just plain
>> wrong (as so often): all the U-Boot versions contain code that is GPLv2
>> without + and that is BSD-3c, some also contain code that is eCos-2.0,
>> IBM-pibs, LGPL. So we should probably fix the license spec for U-Boot
>> regardless of where it comes from.
>
> The U-Boot licenses that apply rely on the selected target too which
> complicates things.
> I don't think we want to become license police here other than "one or
> more of X, Y, ..., please do your homework".
I agree completely. But currently it just says GPLv2+, which is plain
wrong.
Regards,
Arnout
> Regards.
>
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind 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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-10-24 19:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 14:37 [Buildroot] [PATCH] uboot-tools: fix license issues Gustavo Zacarias
2013-10-22 14:57 ` Thomas De Schampheleire
2013-10-22 15:22 ` Gustavo Zacarias
2013-10-23 9:39 ` Thomas Petazzoni
2013-10-24 6:51 ` Thomas De Schampheleire
2013-10-24 8:20 ` Luca Ceresoli
2013-10-24 12:24 ` Arnout Vandecappelle
2013-10-24 12:35 ` Gustavo Zacarias
2013-10-24 19:29 ` Arnout Vandecappelle [this message]
2013-10-22 16:39 ` Peter Korsgaard
2013-10-22 16:39 ` Gustavo Zacarias
2013-10-22 17:01 ` Thomas De Schampheleire
2013-10-22 17:49 ` Peter Korsgaard
2013-10-22 17:50 ` Gustavo Zacarias
-- strict thread matches above, loose matches on Subject: below --
2013-10-22 16:46 Gustavo Zacarias
2013-11-02 13:43 ` Thomas Petazzoni
2013-11-02 16:24 ` Gustavo Zacarias
2013-11-02 16:43 ` Thomas Petazzoni
2013-11-02 17:32 ` Yann E. MORIN
2013-11-02 17:38 ` Thomas Petazzoni
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=5269751C.1000207@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