From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Ross Burton <ross.burton@intel.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [master][zeus][PATCHv2] cairo: Adapt license for cairo-dbg and cairo-src based on contents
Date: Sat, 11 Jan 2020 03:19:02 +0000 [thread overview]
Message-ID: <01cc92ebbe524f1cae23acb05e4a5d07@XBOX03.axis.com> (raw)
In-Reply-To: <fabf0714-f1be-16a9-6b47-b065f0f7eaed@intel.com>
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org <openembedded-core-
> bounces@lists.openembedded.org> On Behalf Of Ross Burton
> Sent: den 11 januari 2020 00:28
> To: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [master][zeus][PATCHv2] cairo: Adapt license for
> cairo-dbg and cairo-src based on contents
>
> On 10/01/2020 22:03, 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.
>
> The shortlog makes no mention of trace at all. Can this be split into
> two commits, one for trace and one for the license mangling.
I will split it in two patches.
> The license mangling is quite ugly but I'm not sure if there's a better
> solution...
>
> Ross
//Peter
prev parent reply other threads:[~2020-01-11 3:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 22:03 [master][zeus][PATCHv2] cairo: Adapt license for cairo-dbg and cairo-src based on contents Peter Kjellerstedt
2020-01-10 23:27 ` Ross Burton
2020-01-11 3:19 ` Peter Kjellerstedt [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=01cc92ebbe524f1cae23acb05e4a5d07@XBOX03.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.