Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Watt <jpewhacker@gmail.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [master][zeus][PATCH] cairo: Adapt license for cairo-dbg and cairo-src based on contents
Date: Fri, 10 Jan 2020 16:02:19 -0600	[thread overview]
Message-ID: <7ad2ef47-ddde-a281-013f-48205010a3e8@gmail.com> (raw)
In-Reply-To: <9ebc0390e45449a0a9f9d8859e9a9f5d@XBOX03.axis.com>


On 1/10/20 3:58 PM, Peter Kjellerstedt wrote:
>> -----Original Message-----
>> From: Joshua Watt <jpewhacker@gmail.com>
>> Sent: den 10 januari 2020 16:23
>> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>; openembedded-
>> core@lists.openembedded.org
>> Subject: Re: [OE-core] [master][zeus][PATCH] cairo: Adapt license for
>> cairo-dbg and cairo-src based on contents
>>
>> On 12/5/19 4:26 PM, Peter Kjellerstedt wrote:
>>> Introduce a PACKAGECONFIG "trace" to disable cairo-trace (the only
>>> part of the code licensed as GPL-3.0, and which is normally packaged
>>> separately in cairo-perf-utils). By disabling this, we can adapt the
>>> licenses for cairo-dbg and cairo-src so that they do not include
>>> "GPLv3+" when trace is disabled and thus they can be used also when,
>>> e.g., GPL-3.0 is blacklisted in INCOMPATIBLE_LICENSE.
>> Thanks for this, it fixes a build error I was experiencing. However,
> Out of curiosity, how can it fix a build failure?

As you pointed out in the commit message, it allows image construction 
when INCOMPATIBLE_LICENSE contains "GPL-3.0" :)

>
>> when I apply this patch locally for testing, I get QA errors saying that
>> the "/usr/bin" and "/usr/lib/cairo" directories aren't part of any
>> package. It looks like these directories are empty when trace is
>> disabled and should be removed in do_install ?
> Ok, that's embarrassing. Apparently I had --disable-script in
> EXTRA_OECONF (from a local bbappend we have) when I tested without
> "trace" in PACKAGECONFIG, and apparently that causes cairo-sphinx
> not to be built and thus the /usr/bin and /usr/lib/cairo directories
> are never created.
>
> I'll send an updated patch.
>
> //Peter
>


      reply	other threads:[~2020-01-10 22:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 22:26 [master][zeus][PATCH] cairo: Adapt license for cairo-dbg and cairo-src based on contents Peter Kjellerstedt
2019-12-22 13:00 ` Peter Kjellerstedt
2019-12-22 13:21   ` Alexander Kanavin
2019-12-23  7:54     ` Peter Kjellerstedt
2019-12-22 16:15   ` akuster808
2019-12-23  7:59     ` Peter Kjellerstedt
2020-01-10 15:23 ` Joshua Watt
2020-01-10 21:58   ` Peter Kjellerstedt
2020-01-10 22:02     ` Joshua Watt [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=7ad2ef47-ddde-a281-013f-48205010a3e8@gmail.com \
    --to=jpewhacker@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.com \
    /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