All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Miroshnichenko <sergeimir@emcraft.com>
To: openembedded-core@lists.openembedded.org,
	Mariano Lopez <mariano.lopez@linux.intel.com>
Cc: Roger Meier <r.meier@siemens.com>,
	Alexander Dyachenko <sasha_d@emcraft.com>
Subject: Re: [PATCH v2 0/1] license: Add support for SPDX 2.0 operators
Date: Mon, 11 Jul 2016 11:47:34 +0300	[thread overview]
Message-ID: <57835D26.7070004@emcraft.com> (raw)
In-Reply-To: <1467620748-20129-1-git-send-email-sergeimir@emcraft.com>

ping

Thanks,
Sergei

On 07/04/2016 11:25 AM, Sergei Miroshnichenko wrote:
> Composite SPDX license expressions can be constructed using "OR",
> "AND" and "WITH" operators: map them to "|" and "&" operators
> accordingly.
> 
> Recognize long form license identifiers: "[DocumentRef-XXX:][LicenseRef-]YYY".
> 
> Tested on the following expressions:
> LICENSE = "Artistic-1.0"
> LICENSE = "LicenseRef-Artistic-1.0 AND NASA-1.3"
> LICENSE = "(LicenseRef-Artistic-1.0 WITH GPL-3.0-with-GCC-exception)
>            OR (DocumentRef-spdx-tool-1.2:LicenseRef-NASA-1.3 AND GPL-2.0+)"
> 
> Reference:
> https://spdx.org/sites/spdx/files/SPDX-2.0.pdf Appendix IV: SPDX License Expression
> 
> Sergei Miroshnichenko (1):
>   license: Add support for SPDX 2.0 operators
> 
>  meta/classes/license.bbclass | 17 ++++++++++-------
>  meta/lib/oe/license.py       | 21 ++++++++++++++++-----
>  2 files changed, 26 insertions(+), 12 deletions(-)
> 


      parent reply	other threads:[~2016-07-11  8:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04  8:25 [PATCH v2 0/1] license: Add support for SPDX 2.0 operators Sergei Miroshnichenko
2016-07-04  8:25 ` [PATCH v2 1/1] " Sergei Miroshnichenko
2016-07-11  8:47 ` Sergei Miroshnichenko [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=57835D26.7070004@emcraft.com \
    --to=sergeimir@emcraft.com \
    --cc=mariano.lopez@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=r.meier@siemens.com \
    --cc=sasha_d@emcraft.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.