From: <Mikko.Rapeli@bmw.de>
To: <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 2/2] license_image.bbclass: check and reject packages which have incompatible licenses
Date: Thu, 10 Oct 2019 07:41:44 +0000 [thread overview]
Message-ID: <20191010074144.GF2964@hiutale> (raw)
In-Reply-To: <CANNYZj_AC=6LdUgvW7DZ=gJzDwejnEJX0WpJztoCiTXkX08vEQ@mail.gmail.com>
On Wed, Oct 09, 2019 at 09:41:28PM +0200, Alexander Kanavin wrote:
> It wouldn't be too hard to add a condition that checks the (image-specific)
> whitelist, I just wanted to gather a bit of feedback for the overall idea :)
I like the idea. I'm building images with e.g. GPLv3 forbidden but I enable building
lots of GPLv3 components because they are needed in e.g. ptests. Resulting distro
config snippet is large with lots of lines like:
WHITELIST_GPL-3.0 += "autoconf"
PACKAGE_EXCLUDE += "autoconf-dbg autoconf-staticdev autoconf-dev autoconf-doc autoconf-locale autoconf"
WHITELIST_GPL-3.0 += "ccache"
PACKAGE_EXCLUDE += "ccache-sdktests-dbg ccache-sdktests ccache-dbg ccache-staticdev ccache-dev ccache-doc ccache-locale ccache"
In testing then I start with the pure product image without GPLv3 components and extend it
with extra packages which are needed for the test execution. I have separate product
feature and SW component test phases. Only in the latter case target SW is changed before
test execution.
I want to avoid building separate test images with GPLv3, because in the past
test vs. product images resulted in only the test images being actually tested.
But I can see that having separate product and test images from a single build could
be useful.
Thanks for proposing this patch!
-Mikko
prev parent reply other threads:[~2019-10-10 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 14:44 [RFC PATCH 1/2] license.bbclass: split incompatible license check into a helper function Alexander Kanavin
2019-10-09 14:44 ` [RFC PATCH 2/2] license_image.bbclass: check and reject packages which have incompatible licenses Alexander Kanavin
2019-10-09 18:15 ` Christopher Larson
2019-10-09 19:41 ` Alexander Kanavin
2019-10-10 7:41 ` Mikko.Rapeli [this message]
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=20191010074144.GF2964@hiutale \
--to=mikko.rapeli@bmw.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@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