> -Original Message-
> From: Alexander Kanavin [mailto:alexander.kana...@linux.intel.com]
> Sent: den 19 januari 2018 10:26
> To: Boto, Erik (Pelagicore) <erik.b...@pelagicore.com>;
> yocto@yoctoproject.org
> Cc: clemens.l...@bmw-carit.de
> Subject: Re
On 01/19/2018 07:21 AM, Boto, Erik (Pelagicore) wrote:
I was looking for a way to analyze in more detail how packages of different
licenses was used in an image, and stumbled upon this old mail-thread:
https://lists.yoctoproject.org/pipermail/yocto/2015-January/023307.html
My end goal is
Hi,
I was looking for a way to analyze in more detail how packages of different
licenses was used in an image, and stumbled upon this old mail-thread:
https://lists.yoctoproject.org/pipermail/yocto/2015-January/023307.html
My end goal is pretty much the same as Clemens, that I want to be able
Hi Paul,
On Wed, Jan 28, 2015 at 10:25:29AM +, Paul Eggleton wrote:
This sounds like something we should be handling in our
INCOMPATIBLE_LICENSE check code, although it's not clear that we
currently handle where alternatives to an incompatible license are
available for a recipe/package,
Hi,
I have written a bbclass that does license conflict checking before
building images for distribution. I am wondering if that is something
you as a project would be interested in integrating, e.g. into poky.
I am also looking for feedback to my approach and ideas on how to handle
corner
Hi Clemens,
On Wednesday 28 January 2015 09:52:14 Clemens Lang wrote:
I have written a bbclass that does license conflict checking before
building images for distribution. I am wondering if that is something
you as a project would be interested in integrating, e.g. into poky.
I am also
