Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 04/21 RFC] core/legal-info: allow ignoring packages from the legal-info
Date: Tue, 17 Nov 2015 20:28:02 +0100	[thread overview]
Message-ID: <20151117192802.GA3703@free.fr> (raw)
In-Reply-To: <564B655C.5060105@lucaceresoli.net>

Luca, Thomas, All,

On 2015-11-17 18:35 +0100, Luca Ceresoli spake thusly:
> Thomas Petazzoni wrote:
> >On Mon, 16 Nov 2015 23:46:59 +0100, Yann E. MORIN wrote:
> >>It might be necessary to not even mention a package in the output of
> >>legal-info:
> >>
> >>   - virtual package have virtually nothing to save in the legal-info
> >>     output;
> >>
> >>   - for Buildroot itself, host-gcc-initial and host-gcc-final are not
> >>     real packages, they are just two different steps of the same
> >>     package, gcc;
> >>
> >>   - for proprietary packages, it might not even be legal to even mention
> >>     them, being under NDA or some other such restrictive conditions.
> >>
> >>Add the new 'IGNORE' keyword to the _REDISTRIBUTE package variable, so
> >>that the legal-info infra will simply completely ignore that package.
> >>
> >>Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> >>Cc: Luca Ceresoli <luca@lucaceresoli.net>
> >
> >I understand the idea, but I'm not a big fan of a boolean variable that
> >is no longer a boolean variable.
> >
> >So, let me question the current handling of <pkg>_REDISTRIBUTE = NO.
> >Does it make sense to mention such packages in the legal-info output,
> >since their source code is not saved anyway?
> >
> >Shouldn't we simply change the behavior of <pkg>_REDISTRIBUTE = NO to
> >be that such packages are not listed at all in the legal-info output,
> >which would match what you're looking for for with this "IGNORE" thing ?
> >
> >Luca, do you see any drawback in completely omitting REDISTRIBUTE = NO
> >packages from legal-info ?
> 
> Indeed I think we need that behaviour for some binary-only packages.
> imx-vpu looks like a good example. Its COPYING file contains the
> following clause:
> 
> >3.4.             You must reproduce any and all of Freescale's (or its third
> >party licensor's) copyright notices and other proprietary legends on copies of
> >Licensed Software.
> 
> To the best of my understanding this means we must mention the package
> and its legal wording in legal-info.
> 
> Thus your proposed change of meaning for REDISTRIBUTE = NO is probably
> not doable.
> 
> How about changing the entire REDISTRIBUTE meaning from a boolean to an
> enumerative? Values would be:
> 
>  - ALL: equals current YES
>  - METADATA: equals current NO, produces no tarball
>  - NOTHING: equals Yann's IGNORE
>  - YES: deprecated, for backward compatibility
>  - NO: deprecated, for backward compatibility
> 
> In other words, change the meaning of REDISTRIBUTE from "do you want to
> redistribute the tarball?" to "what do you want to redistribute?".

Well, I don't really care whether we call it IGNORE or NOTHING or
whatever makes more sense. I'm also fine with deprecating YES and NO
to replace them with more meaningful values.

What I care about is having the ability to mark a package for the
following conditions:

  - redistribute "source" archive, list in the manifest and save
    licensing files,

  - list in the manifest and save licensing files,

  - completely omit the package from legal-info.

As Luca explained, there are packages for which we should not
redistribute the "source" archive, but which we must list in the
manifest. Luca talked about imx-vpu, I was thinking about
nvidia-driver.

The new possibility that I would want is to completely ignore the
package from the legal-info output, as there might be legal reasons that
the mere existence of that package should not be disclosed.

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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-11-17 19:28 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 22:47 [Buildroot] [PATCH 0/21 RFC] core/legal-info: fixes, completness and enhancements (branch yem/legal-patch) Yann E. MORIN
2015-11-16 22:46 ` [Buildroot] [PATCH 01/21 RFC] package/libecore: do not build anything at patch time Yann E. MORIN
2015-11-17 11:16   ` Thomas Petazzoni
2015-11-17 12:20     ` Romain Naour
2015-11-17 20:16       ` Romain Naour
2015-11-17 16:03   ` Peter Korsgaard
2015-11-16 22:46 ` [Buildroot] [PATCH 02/21 RFC] core/legal-info: fix missing double-$ Yann E. MORIN
2015-11-17 11:19   ` Thomas Petazzoni
2015-11-17 16:03   ` Peter Korsgaard
2015-11-16 22:46 ` [Buildroot] [PATCH 03/21 RFC] package/linux-headers: add licensing information Yann E. MORIN
2015-11-17 11:19   ` Thomas Petazzoni
2015-11-17 16:04   ` Peter Korsgaard
2015-11-16 22:46 ` [Buildroot] [PATCH 04/21 RFC] core/legal-info: allow ignoring packages from the legal-info Yann E. MORIN
2015-11-17 11:22   ` Thomas Petazzoni
2015-11-17 17:35     ` Luca Ceresoli
2015-11-17 19:28       ` Yann E. MORIN [this message]
2015-11-17 20:14         ` Thomas Petazzoni
2015-11-17 21:26           ` Yann E. MORIN
2015-11-17 21:43     ` Arnout Vandecappelle
2015-11-17 21:48   ` Arnout Vandecappelle
2015-11-16 22:47 ` [Buildroot] [PATCH 05/21 RFC] core/pkg-virtual: ignore from legal-info output Yann E. MORIN
2015-11-17 11:25   ` Thomas Petazzoni
2015-11-17 19:35     ` Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 06/21 RFC] package/gcc: add licensing information Yann E. MORIN
2015-11-17 11:28   ` Thomas Petazzoni
2015-11-17 21:15     ` Yann E. MORIN
2015-11-17 21:25       ` Thomas Petazzoni
2015-11-17 21:40         ` Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 07/21 RFC] package/gcc: handle " Yann E. MORIN
2015-11-17 11:31   ` Thomas Petazzoni
2015-11-17 21:20     ` Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 08/21 RFC] package/gcc: add a patch for arc rather than using sed Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 09/21 RFC] package/gcc: properly extract and patch sources Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 10/21 RFC] package/gcc: make host-gcc a pure host package Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 11/21 RFC] package/gcc: make -initial and -final use sources from host-gcc Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 12/21 RFC] package/gcc: include the extensa overlay in the legal-info output Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 13/21 RFC] package/perl: include perl-cross " Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 14/21 RFC] core: add a global variable with already-unquoted global patch dir Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 15/21 RFC] core/pkg-generic: add macro to hardlink-or-copy Yann E. MORIN
2015-11-18 15:40   ` Luca Ceresoli
2015-11-16 22:47 ` [Buildroot] [PATCH 16/21 RFC] core/legal-info: use the macro to install source archives Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 17/21 RFC] core/legal-info: install source archives in their own sub-dir Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 18/21 RFC] core/legal-info: add package version to license directory Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 19/21 RFC] core/apply-patches: store full path of applied patches Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 20/21 RFC] core/legal-info: also save patches Yann E. MORIN
2015-11-16 22:47 ` [Buildroot] [PATCH 21/21 RFC] core/pkg-infra: ensure legal-info works in off-line mode Yann E. MORIN

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=20151117192802.GA3703@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