All of lore.kernel.org
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] recipetool/create.py: fix LICENSE value
Date: Thu, 23 Jun 2016 09:30:26 +0800	[thread overview]
Message-ID: <576B3BB2.4090604@windriver.com> (raw)
In-Reply-To: <CAJTo0LYpa5AMtaiOT_9L851vTyMbcNuPSWjdvmWQJq=EhJYzhA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]

On 06/22/2016 06:57 PM, Burton, Ross wrote:
>
> On 16 June 2016 at 10:30, Chen Qi <Qi.Chen@windriver.com 
> <mailto:Qi.Chen@windriver.com>> wrote:
>
>     When there multiple license in a repo, the LICENSE value be created as
>     something like "LGPLv2.1 GPLv2", which causes the following warning.
>
>     LICENSE value "LGPLv2.1 GPLv2" has an invalid format - license
>     names must
>     be separated by the following characters to indicate the license
>     selection: &|()
>
>     Fix it by using '&' to join multiple licenses.
>
>
> This behaviour is intentional, as recipetool isn't smart enough to 
> read the licensing terms and decide if there are multiple licenses in 
> aggregate (&) or a choice of licenses (|).  The solution is to list 
> all the licenses that have been found, let bitbake throw a warning, 
> and the person creating a recipe comprehend the licensing situation 
> and add the relevant operations.
>
> Ross

Thanks for your detailed explanation.

Best Regards,
Chen Qi

[-- Attachment #2: Type: text/html, Size: 2329 bytes --]

      reply	other threads:[~2016-06-23  1:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16  9:30 [PATCH 0/1] recipetool/create.py: fix LICENSE value Chen Qi
2016-06-16  9:30 ` [PATCH 1/1] " Chen Qi
2016-06-22 10:57   ` Burton, Ross
2016-06-23  1:30     ` ChenQi [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=576B3BB2.4090604@windriver.com \
    --to=qi.chen@windriver.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.