All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Gherzan <andrei@gherzan.ro>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] license.bbclass base.bbclass: support for 'or' operand in LICENSE and for SPDX license names
Date: Tue, 10 Jan 2012 18:07:23 +0200	[thread overview]
Message-ID: <4F0C623B.7050209@gherzan.ro> (raw)
In-Reply-To: <CABcZANnzU_5LTeRV=UjPiUWn6rqnZS6RR_yhsUKE_C_ap-PZ9g@mail.gmail.com>

On 01/10/2012 05:34 PM, Chris Larson wrote:
> On Tue, Jan 10, 2012 at 8:17 AM, Andrei Gherzan<andrei@gherzan.ro>  wrote:
>> From: Andrei Gherzan<andrei.gherzan@windriver.com>
>>
>> A new function was defined in license.bbclass in order to correctly exclude packages where OE-Style licence naming
>> is used. In this way licenses as GPL-3, GPLv3, GPLv3.0 etc will be excluded from a non-GPLv3 build. This function
>> takes into consideration if 'or' operand is used.
>> The function defined in license.bbclass is called in base.bbclass where packages are excluded based on
>> INCOMPATIBLE_LICENSE variable.
>>
>> [YOCTO #1884]
>> [YOCTO #1844]
>>
>> Signed-off-by: Andrei Gherzan<andrei at gherzan.ro>
>
> Out of curiosity, why are we using regex for this when we already have
> license parsing in the oe.license module which can handle the OR case?

I'm using regex only for excluding '+' characters from LICENSE. The rest 
of the work is done in oe.license.
If X is defined as INCOMPATIBLE_LICENSE, X+ should be exluded as well.




  reply	other threads:[~2012-01-10 16:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 15:17 [PATCH] license.bbclass base.bbclass: support for 'or' operand in LICENSE and for SPDX license names Andrei Gherzan
2012-01-10 15:34 ` Chris Larson
2012-01-10 16:07   ` Andrei Gherzan [this message]
2012-01-10 16:10     ` Chris Larson
2012-01-10 16:12       ` Andrei Gherzan
2012-01-10 16:34         ` Chris Larson
2012-01-10 16:55           ` Flanagan, Elizabeth
2012-01-10 17:05             ` Chris Larson
2012-01-10 18:13           ` Andrei Gherzan
2012-01-10 18:54             ` Chris Larson
2012-01-12  6:44 ` Saul Wold

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=4F0C623B.7050209@gherzan.ro \
    --to=andrei@gherzan.ro \
    --cc=openembedded-core@lists.openembedded.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.