On 6/30/20 3:07 AM, Mikko Rapeli wrote:
Hi,
On Tue, Jun 30, 2020 at 09:34:39AM +, John Ernberg 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
It goes over a list of packages installed into their image, and checks
their licensing. If something was directly built into something else, it
will not produce a separate package, and therefore you need to handle that
separately: perhaps by setting the package license appropriately in
respective
Hi,
On Tue, Jun 30, 2020 at 09:34:39AM +, John Ernberg 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
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 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,
