From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gustavo Zacarias Date: Thu, 24 Oct 2013 09:35:08 -0300 Subject: [Buildroot] [PATCH] uboot-tools: fix license issues In-Reply-To: <52691180.9070908@mind.be> References: <1382452676-2514-1-git-send-email-gustavo@zacarias.com.ar> <20131023113944.2e370a3b@skate> <2e6a07b0-2c59-47f7-a320-9f4ba3ddffe2@email.android.com> <52691180.9070908@mind.be> Message-ID: <526913FC.7070905@zacarias.com.ar> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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. And there's custom tarball / git repo / etc too. > 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". Regards.