All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Larson <clarson@kergoth.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: LICENSE_{X}-xxx is parsed?
Date: Tue, 24 Apr 2012 15:53:34 -0700	[thread overview]
Message-ID: <CABcZANnyFDurr+B6nW5nJz+3kq2RXp4403Eqhcahkt53ififeA@mail.gmail.com> (raw)
In-Reply-To: <CAPhnLPCWAKLiLUfKVaguN_cFA=PAgRhW4vZ-pa1XDtW=Wugvpg@mail.gmail.com>

On Tue, Apr 24, 2012 at 3:38 PM, Flanagan, Elizabeth
<elizabeth.flanagan@intel.com> wrote:
> The rest of the packages in the bb should be inheriting LICENSE if no
> PN level license is set. Which obviously causes problems for the above
> example.
>
> In a case like above you'd want to do either of the following:
>
> a. Call out each package's license individually (better but can be
> painful for recipes with lots of packages)
> b. Leave GPLv3 out of LICENSE (easier but not technically accurate) so
> undefined package level licensing inherits the correct LICENSE.

I wonder if a partially specified set of individual package settings
should be identified by some sanity check (an explicit, rather than
implicit, one, like recipe_sanity) as a potential bug / source of
confusion. I suspect most of the time it should be one or the other,
either no individual package LICENSEs are defined, or they all should
be.
-- 
Christopher Larson



  reply	other threads:[~2012-04-24 23:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 17:25 LICENSE_{X}-xxx is parsed? Andrei Gherzan
2012-04-24 17:44 ` Flanagan, Elizabeth
2012-04-24 21:15   ` Andrei Gherzan
2012-04-24 21:25     ` Andrei Gherzan
2012-04-24 22:38     ` Flanagan, Elizabeth
2012-04-24 22:53       ` Chris Larson [this message]
2012-04-24 23:13         ` Flanagan, Elizabeth
2012-04-25  8:17           ` Richard Purdie
2012-04-25 16:04             ` Flanagan, Elizabeth

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=CABcZANnyFDurr+B6nW5nJz+3kq2RXp4403Eqhcahkt53ififeA@mail.gmail.com \
    --to=clarson@kergoth.com \
    --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.