From: "John Ernberg" <john.ernberg@actia.se>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] INCOMPATIBLE_LICENSE - how to use it properly?
Date: Tue, 30 Jun 2020 10:01:56 +0000 [thread overview]
Message-ID: <01d5b9db-cd7e-eee9-bc09-1ff346c7e2aa@actia.se> (raw)
In-Reply-To: <CANNYZj9jEMyhwHFoSsjPQbLV7ff=336_JYcaJ=NTJ1Smcyuz9w@mail.gmail.com>
Hi Alex,
I will give this a try on master.
One question though, will this still catch build-only libraries? (i.e. a
library that consists only of headers). I don't think we have such
recipes right now, it's more to understand how this feature works.
Thank you.
Best regards // John Ernberg
On 6/30/20 11:55 AM, Alexander Kanavin wrote:
> On master, you can set INCOMPATIBLE_LICENSE in the image recipe, rather
> than globally, then the check would only be performed on items that
> actually go into that image.
>
> Warrior does not have that feature yet, I think, so your only option
> there is meta-gpl2.
>
> Alex
>
> On Tue, 30 Jun 2020 at 11:34, John Ernberg <john.ernberg@actia.se
> <mailto:john.ernberg@actia.se>> wrote:
>
> Hi,
>
> I have been trying to use INCOMPATIBLE_LICENSE to filter out
> undesirable
> licenses for us from our images. I started simple and picked the
> examples from the manual (AGPL-3.0, GPL-3.0 and LGPL-3.0).
>
> Currently we're based on Warrior, but I also did a short test on master
> (results later in the message)
>
> Our images use systemd as init system. We use busybox ash as shell on
> these images for now.
>
> When setting the INCOMPATIBLE_LICENSE according to the manual example,
> systemd cannot be built anymore because bash is being skipped due to
> license.
>
> Turns out that because systemd-bash-completion and
> systemd-kernel-install both rdepend on bash, we can't build systemd at
> all, because bash is not buildable. Even if we're not installing those
> features of systemd.
>
> A dive into TaskData suggests that all the rdepends of all packages
> provided by a recipe are flattened into depends of the recipe when
> testing buildability.
>
> A quick test on master from about 2 weeks ago show the same behavior.
>
> For the test on master all I did was change the DISTRO_FEATURES of
> core-image-minimal to include systemd.
>
>
> Am I using ICOMPATIBLE_LICENSE properly so far?
> If so, is being unable to fulfill an rdepend for an unused package
> meant
> to fail the whole build, and how can I avoid it short of including
> meta-gplv2 or writing lots of .bbappends to remove the dependencies?
> Otherwise, where did I go wrong, and what should I be trying instead?
>
> Thank you.
>
> Best regards // John Ernberg
>
>
next prev parent reply other threads:[~2020-06-30 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 9:34 INCOMPATIBLE_LICENSE - how to use it properly? John Ernberg
2020-06-30 9:55 ` [yocto] " Alexander Kanavin
2020-06-30 10:01 ` John Ernberg [this message]
2020-06-30 10:31 ` Alexander Kanavin
2020-06-30 10:07 ` Mikko Rapeli
2020-06-30 21:52 ` Khem Raj
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=01d5b9db-cd7e-eee9-bc09-1ff346c7e2aa@actia.se \
--to=john.ernberg@actia.se \
--cc=alex.kanavin@gmail.com \
--cc=yocto@lists.yoctoproject.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