From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Some legal-info observations/problems
Date: Wed, 02 Oct 2013 16:22:22 +0200 [thread overview]
Message-ID: <871u43rbvl.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAAXf6LXHXo2vY8ns61fxoLzD0n2yzLASZqFk75xzYQwgDHp15Q@mail.gmail.com> (Thomas De Schampheleire's message of "Wed, 2 Oct 2013 16:06:13 +0200")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:
Thomas> Hi,
Thomas> I am starting to use the legal-info infrastructure now, and this
Thomas> resulted in a number of observations/problems, which I'll list below.
Thomas> 1. there is no longer a provision to 'hide' proprietary packages from
Thomas> the manifest, and not get warnings on them. Previously you could mark
Thomas> a package as license: PROPRIETARY, but this has been removed. I still
Thomas> think that a similar feature is useful.
Thomas> 2. suppose FOO_LICENSE_FILES = subdir/COPYING, then the manifest also
Thomas> contains the string 'subdir/COPYING'. However, the license is copied
Thomas> into a flat structure output/legal-info/licenses/foo/, so I think that
Thomas> the manifest should no longer mention the 'subdir'.
Thomas> Of course, this may contradict with the needs of licenses.txt (the
Thomas> flat representation of all licenses) that does not suffer from the
Thomas> subdir problem.
Thomas> 3. partially related to point 2: if a package has multiple license
Thomas> files with the same name but in subdirectories, e.g. a/COPYING and
Thomas> b/COPYING, the copying of the license will copy both files on top of
Thomas> each other. This is the case for xenomai-forge (not yet in buildroot),
Thomas> which is the new strategy for xenomai [1]. I have brought up this
Thomas> issue with the developers [2], but maybe there is something else we
Thomas> can do.
Do you still see this after 31aa4264d8839d0?
Author: Peter Korsgaard <jacmet@sunsite.dk>
Date: Wed Jun 5 10:52:18 2013 +0200
pkg-utils.mk: legal-license-file: handle multiple license files with same name
Some packages (kmod, e2fsprogs, ..) contain multiple (different) license
files with the same file name, but in different directories.
These are currently all copied to the same filename in
output/legal-info/licenses/<pkg>, overwriting everything but the last file.
Fix it by recreating the same directory structure under legal-info.
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-10-02 14:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 14:06 [Buildroot] Some legal-info observations/problems Thomas De Schampheleire
2013-10-02 14:22 ` Peter Korsgaard [this message]
2013-10-02 14:32 ` Thomas De Schampheleire
2013-10-02 15:23 ` Thomas Petazzoni
2013-10-02 16:33 ` Luca Ceresoli
2013-10-03 8:24 ` Thomas De Schampheleire
2013-10-03 16:40 ` Arnout Vandecappelle
2013-10-04 8:54 ` Thomas De Schampheleire
2013-10-04 9:07 ` Thomas Petazzoni
2013-10-04 15:30 ` Ryan Barnett
2013-10-04 15:34 ` Thomas Petazzoni
2013-10-04 15:39 ` Ryan Barnett
2013-10-04 15:46 ` Simon Dawson
2013-10-07 22:43 ` Arnout Vandecappelle
2013-10-09 7:23 ` Simon Dawson
2013-10-09 7:29 ` Thomas Petazzoni
2013-10-09 7:31 ` Simon Dawson
2013-10-05 21:07 ` Luca Ceresoli
2013-10-02 16:31 ` Arnout Vandecappelle
2013-10-03 8:30 ` Thomas De Schampheleire
2013-10-02 18:49 ` Ryan Barnett
2013-10-03 8:34 ` Thomas De Schampheleire
2013-10-03 13:31 ` Ryan Barnett
2013-10-03 13:42 ` Danomi Manchego
2013-10-03 14:12 ` Ryan Barnett
2013-10-03 16:50 ` Arnout Vandecappelle
2013-10-03 21:38 ` Peter Korsgaard
2013-10-03 22:44 ` Ryan Barnett
2013-10-07 8:19 ` Thomas De Schampheleire
2013-10-09 13:14 ` Luca Ceresoli
2013-10-09 16:46 ` Arnout Vandecappelle
2013-10-11 14:13 ` Thomas De Schampheleire
2013-10-09 19:54 ` Ryan Barnett
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=871u43rbvl.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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