From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] core/legal-info: allow ignoring packages from the legal-info
Date: Sat, 15 Oct 2016 19:36:11 +0200 [thread overview]
Message-ID: <87d1j1a510.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <18b75237-c88f-586e-347c-d1c1a1d15cd5@mind.be> (Arnout Vandecappelle's message of "Sat, 15 Oct 2016 19:22:26 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>>
>> * FOO_GEN_LEGAL_INFO = NO: save nothing
>> * FOO_GEN_LEGAL_INFO = YES, FOO_REDISTRIBUTE = NO: list only
>> * FOO_GEN_LEGAL_INFO = YES, FOO_REDISTRIBUTE = NO: list + save source
The last is presumably FOO_REDISTRIBUTE = YES.
> I hate that we have all these combinations. That was actually my first thought
> when I saw this patch: oh no, yet another variation point. But I don't see a way
> to simplify it. So OK.
yeah, me too. I also cannot think of a simpler approach if we want to do
it.
I don't think it is really a big deal to list the virtual packages in
the legal info, and people doing funky stuff in br2-external can also
post process their legal info data to remove unwanted stuff if needed.
But OK, it doesn't add a lot of complexity, so if others think it is
worthwhile, I'm OK with it as well.
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-10-15 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 13:28 [Buildroot] [PATCH] core/legal-info: allow ignoring packages from the legal-info Yann E. MORIN
2016-10-15 14:58 ` Samuel Martin
2016-10-15 15:03 ` Yann E. MORIN
2016-10-15 15:13 ` Peter Korsgaard
2016-10-15 15:32 ` Yann E. MORIN
2016-10-15 15:40 ` Luca Ceresoli
2016-10-15 15:45 ` Yann E. MORIN
2016-10-15 17:22 ` Arnout Vandecappelle
2016-10-15 17:36 ` Peter Korsgaard [this message]
2016-10-15 17:37 ` Yann E. MORIN
2016-10-15 18:06 ` Arnout Vandecappelle
2016-10-15 20:13 ` Yann E. MORIN
2016-10-17 8:22 ` Luca Ceresoli
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=87d1j1a510.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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