From: <Mikko.Rapeli@bmw.de>
To: <alex.kanavin@gmail.com>
Cc: <armccurdy@gmail.com>, <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:16:10 +0000 [thread overview]
Message-ID: <Yg9VyQM8LrfUotvf@korppu> (raw)
In-Reply-To: <CANNYZj9SjKwzhBrpphqLkNCLOieZUs_Z+r-80yriWJV3xAzErQ@mail.gmail.com>
Hi,
On Fri, Feb 18, 2022 at 09:03:53AM +0100, Alexander Kanavin wrote:
> You should really try per-image INCOMPATIBLE_LICENSE :) Maintaining
> those whitelists/excludes is awkward, as developers constantly want
> more of them.
Hmm, this rings a bell. Likely yes then :)
But on the other hand this way we're quite explicit about what GPLv3 things
we allow to compile. Compiling too much also hurts with compilation times too and for
many use cases developers are better off working with Debian or Ubuntu tooling than
compiling every bell and whistle with yocto.
My list of GPLv3 recipes enabled for compilation is quite stable at:
autoconf
bash
bc
binutils
bison
cairo
ccache
coreutils
diffutils
elfutils
findutils
gawk
gcc
gdb
gdbm
gettext
gnutls
grep
libevent
libmpc
libpipeline
libunistring
m4
make
mpfr
python-rfc3987
python-strict-rfc3339
readline
rsync
sed
tcpreplay
which
Cheers,
-Mikko
next prev parent reply other threads:[~2022-02-18 8:16 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 ` [Openembedded-architecture] " Mikko.Rapeli
2022-02-18 8:03 ` Alexander Kanavin
2022-02-18 8:16 ` Mikko.Rapeli [this message]
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=Yg9VyQM8LrfUotvf@korppu \
--to=mikko.rapeli@bmw.de \
--cc=Saul.Wold@windriver.com \
--cc=alex.kanavin@gmail.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