From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Saul Wold <Saul.Wold@windriver.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] [RFC PATCH] Rename INCOMPATIBLE related varibale
Date: Thu, 17 Feb 2022 14:06:29 +0000 [thread overview]
Message-ID: <262e7eaec4e44237abf3f0f7853d6f6f@axis.com> (raw)
In-Reply-To: <35c7accdbd700eb31e9728fc4f773c648695bff9.camel@linuxfoundation.org>
> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Richard Purdie
> Sent: den 17 februari 2022 11:44
> To: Saul Wold <Saul.Wold@windriver.com>; openembedded-
> core@lists.openembedded.org
> Subject: Re: [OE-core] [RFC PATCH] Rename INCOMPATIBLE related varibale
>
> On Wed, 2022-02-16 at 15:52 -0800, Saul Wold wrote:
> > This is one option to handle the rename, another alternative would
> > be to change the new INCOMPATIBLE_LICENSE_ALLOWED_RECIPES to VarFlag
> > style.
>
> It is one option but I'm not sure it makes sense. This functionality
> is a bit of a historical relic and the syntax is absolutely horrible.
> If we're going to change it, I'd like to take the opportunity to step
> back and fix it somehow. I've not spent the time thinking what that
> might look like unfortunately.
>
> Cheers,
>
> Richard
I definitely agree that the system for handling compatible/incompatible
licenses need to be reworked. I sent a longish response to Jon's mail
on the yocto list January 29 where I discussed this.
//Peter
prev parent reply other threads:[~2022-02-17 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 23:52 [RFC PATCH] Rename INCOMPATIBLE related varibale Saul Wold
2022-02-17 10:43 ` [OE-core] " Richard Purdie
2022-02-17 14:06 ` 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=262e7eaec4e44237abf3f0f7853d6f6f@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=Saul.Wold@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 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.