Openembedded Core Discussions
 help / color / mirror / Atom feed
From: <Mikko.Rapeli@bmw.de>
To: <armccurdy@gmail.com>
Cc: <Saul.Wold@windriver.com>,
	<openembedded-architecture@lists.openembedded.org>,
	<openembedded-core@lists.openembedded.org>,
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] [oe] INCOMPATIBLE_LICENSES and WHITELIST_<license> usage
Date: Fri, 18 Feb 2022 08:00:28 +0000	[thread overview]
Message-ID: <Yg9SGkkOMwoPVcP1@korppu> (raw)
In-Reply-To: <CAJ86T=VF+6J3UBJ-=rYt=rODkdP=H73cWFXyE0YfJCaYJfb1oQ@mail.gmail.com>

Hi,

On Thu, Feb 17, 2022 at 04:20:01PM -0800, Andre McCurdy wrote:
> On Thu, Feb 17, 2022 at 3:01 PM Saul Wold <Saul.Wold@windriver.com> wrote:
> >
> > Folks,
> >
> > I am working on a proposal to re-write how INCOMPATIBLE_LICENSES is used
> > and processed to possibly include a COMPATIBLE_LICENSES variable as
> > well, see PeterK's email [0]
> >
> > I am trying to determine the usage of WHITELIST_<license> which would be
> > used to override a license that might be listed in INCOMPATIBLE_LICENSES
> > variable.
> >
> > Randy and I have done a quick and dirty survey of a 100 or so layers
> > (thanks Randy) and could not find any real usage other than what's
> > currently in OE-Core for WHITELIST_GPL-3.0.
> >
> > If you are using WHITELIST_<license>, please let me reply with your usage.
> 
> Common case seems to be allowing gdb in debug builds of distros which
> are otherwise free of GPLv3 etc, e.g.
> 
>   https://github.com/MentorEmbedded/meta-mentor/blob/master/meta-mel/conf/distro/include/gdbserver-gplv3.inc
>   https://github.com/lgirdk/meta-mng/blob/ofw-2112.6/conf/distro/mng.conf

Exactly, I'm using this in a lot of projects.

Basically distro config has:

INCOMPATIBLE_LICENSE_append += " GPLv3 GPLv3+ LGPLv3 LGPLv3+"

and then various GPLv3 tools are allowed in build but not allowed to be
part of images:

WHITELIST_GPL-3.0 += "binutils"
PACKAGE_EXCLUDE += "binutils-dbg binutils-staticdev binutils-dev binutils-doc binutils-locale libbfd binutils"

WHITELIST_GPL-3.0 += "gdb"
PACKAGE_EXCLUDE += "gdb-sdktests-dbg gdb-sdktests gdbserver gdb-dbg gdb-staticdev gdb-dev gdb-doc gdb-locale gdb"

WHITELIST_GPL-3.0 += "rsync"
PACKAGE_EXCLUDE += "rsync-dbg rsync-staticdev rsync-dev rsync-doc rsync-locale rsync"

etc etc.

Use case is that developers can install additional GPLv3 licensed tooling if they
need to debug something, but product images don't include them by default.

Cheers,

-Mikko

  reply	other threads:[~2022-02-18  8:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 23:01 INCOMPATIBLE_LICENSES and WHITELIST_<license> usage Saul Wold
2022-02-18  0:20 ` [oe] " Andre McCurdy
2022-02-18  8:00   ` Mikko.Rapeli [this message]
2022-02-18  8:03     ` [Openembedded-architecture] " Alexander Kanavin
2022-02-18  8:16       ` Mikko.Rapeli
2022-02-18 14:13 ` Richard Purdie
2022-02-18 23:34   ` Peter Kjellerstedt
2022-02-19  0:44     ` Richard Purdie
2022-02-19  4:42       ` Peter Kjellerstedt
     [not found] ` <16D4E6E0715A89F5.27450@lists.openembedded.org>
2022-02-18 14:24   ` [OE-core] " Richard Purdie

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=Yg9SGkkOMwoPVcP1@korppu \
    --to=mikko.rapeli@bmw.de \
    --cc=Saul.Wold@windriver.com \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-architecture@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /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