From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] core/legal-info: allow ignoring packages from the legal-info
Date: Sat, 15 Oct 2016 22:13:28 +0200 [thread overview]
Message-ID: <20161015201327.GA3982@free.fr> (raw)
In-Reply-To: <520a1ab5-06bb-7a22-1ace-7b4d1febc2c1@mind.be>
Arnout, All,
On 2016-10-15 20:06 +0200, Arnout Vandecappelle spake thusly:
> On 15-10-16 19:37, Yann E. MORIN wrote:
> > On 2016-10-15 19:22 +0200, Arnout Vandecappelle spake thusly:
> >> On 15-10-16 17:40, Luca Ceresoli wrote:
[--SNIP--]
> >>> I suggest listing the three possible cases:
> >>> * 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
> >> 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.
> > The alternative would be:
> > - get rid of LIBFOO_REDISTRIBUTE
> > - add LIBFOO_LEGAL_INFO = {IGNORE,LIST,FULL} (or whatever name/values).
> >
> > Thomas, Peter and Luca were not very happy with such a tristate, and in
> > retrospect, neither am I...
> Neither am I.
Eh! ;-)
> >> One remark though: I think the pre- and post-hooks should still run even if
> >> _GEN_LEGAL_INFO = NO.
> > Not so sure... Such hooks are made to save extra stuff into legal-info,
> > or to prepare the package for legal-info. So, if the package is excluded
> > for legal-info, there is no reason to run those hooks to start with, is
> > there?
> First of all, both _GEN_LEGAL_INFO and _LEGAL_INFO_HOOKS are package-specific
> so the package knows what it's doing.
>
> The reason to run hooks is that you may still want to do *something* in the
> legal info for excluded packages. I can't give a concrete example, but I'm
> thinking along the lines of e.g. doing some check and erroring out, or still
> adding some custom information to legal info. You know, what the hooks are meant
> for in the first place :-) The point is, this option disables the normal
> legal-info, but that doesn't mean that there would be no legal-info at all.
I would argue that, if a packager elected to have its package completely
ignored by the legal-info infra, we should just abide by this wish and
just completely ignore it. Altogether.
Let's see what others think... ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-10-15 20:13 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
2016-10-15 17:37 ` Yann E. MORIN
2016-10-15 18:06 ` Arnout Vandecappelle
2016-10-15 20:13 ` Yann E. MORIN [this message]
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=20161015201327.GA3982@free.fr \
--to=yann.morin.1998@free.fr \
--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