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 19:37:29 +0200 [thread overview]
Message-ID: <20161015173729.GI3668@free.fr> (raw)
In-Reply-To: <18b75237-c88f-586e-347c-d1c1a1d15cd5@mind.be>
Arnout, All,
On 2016-10-15 19:22 +0200, Arnout Vandecappelle spake thusly:
> On 15-10-16 17:40, Luca Ceresoli wrote:
> > On 15/10/2016 17:32, Yann E. MORIN wrote:
> >> Peter, All,
> >>
> >> On 2016-10-15 17:13 +0200, Peter Korsgaard spake thusly:
> >>>>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> >>>
> >>> > It might be necessary to not even mention a package in the output of
> >>> > legal-info:
> >>>
> >>> > - virtual packages have virtually nothing to save in the legal-info
> >>> > output;
> >>>
> >>> > - for proprietary packages, it might not even be legal to even
> >>> > mention them, being under NDA or some other such restrictive
> >>> > conditions.
> >>>
> >>> > Introduce the new FOO_GEN_LEGAL_INFO variable that a package can set
> >>> > to 'NO' (default to 'YES') to indicate that the package should be
> >>> > completely ignored from the legal-info output, in which case the
> >>> > package is not mentioned in the maniufest, its source archive,
> >>> > patches and license files are not saved into legal-info/ .
> >>>
> >>> Couldn't / shouldn't the 2nd part already be handled by
> >>> <foo>_REDISTRIBUTE = NO and/or <foo>_LICENSE = PROPRIETARY?
> >>
> >> No, because for a proprietary license, you may still have to at least
> >> list it in the manifest.
> >>
> >> For example, the nvidia-driver package has a proprietary license, is not
> >> redistributable, but we must still list it in the manifest.
> >>
> >> I'll update the commit log accordingly. Thanks! ;-)
> >
> > 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...
> 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?
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 17:37 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 [this message]
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=20161015173729.GI3668@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