From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/8] License Fixes.
Date: Sun, 25 Mar 2012 11:10:30 +0100 [thread overview]
Message-ID: <1332670230.28414.70.camel@ted> (raw)
In-Reply-To: <cover.1332546190.git.elizabeth.flanagan@intel.com>
On Fri, 2012-03-23 at 16:51 -0700, Beth Flanagan wrote:
> This patchset covers three main topics. The first, and most important is how
> INCOMPATIBLE_LICENSE deals with LICENSE naming variations and pkg level licensing.
>
> We now have the ability to set the recipe level license to one that is inherited by
> all packages as well as the ability to override the main license. This allows us to
> specify that some packages may have incompatible licenses or the recipe may be
> incompatible, but the package itself isn't. I've included an example of this in
> util-license.
>
> Also included are fixes to the last of the license warnings.
>
> And lastly, I've corrected some whitespace within license.bbclass according to the
> style guide.
>
> The following changes since commit 6c77a0f0fa0c97bfbe93f4a930a1549566a7f016:
>
> taglib: Refresh patch after recent accidental breakage (2012-03-23 18:36:20 +0000)
>
> are available in the git repository at:
> git://git.yoctoproject.org/poky-contrib eflanagan/incompatible_license
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=eflanagan/incompatible_license
>
> Elizabeth Flanagan (8):
> license.bbclass: Add spdx mapping to GPL-1.0
> license.bbclass: Whitespace standardization
> INCOMPATIBLE_LICENSE: support for spdx and pkg licenses
> util-linux: Example of pkg level INCOMPATIBLE_LICENSE
> license.bbclass: Style guide compliance
> common-licenses: Adding GPL-2.0-with-OpenSSL-exception
> common-license: Add ICU generic
> setserial: Correct LICENSE
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-03-25 10:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 23:51 [PATCH 0/8] License Fixes Beth Flanagan
2012-03-23 23:51 ` [PATCH 1/8] license.bbclass: Add spdx mapping to GPL-1.0 Beth Flanagan
2012-03-23 23:51 ` [PATCH 2/8] license.bbclass: Whitespace standardization Beth Flanagan
2012-03-23 23:51 ` [PATCH 3/8] INCOMPATIBLE_LICENSE: support for spdx and pkg licenses Beth Flanagan
2012-03-23 23:51 ` [PATCH 4/8] util-linux: Example of pkg level INCOMPATIBLE_LICENSE Beth Flanagan
2012-03-23 23:51 ` [PATCH 5/8] license.bbclass: Style guide compliance Beth Flanagan
2012-03-23 23:51 ` [PATCH 6/8] common-licenses: Adding GPL-2.0-with-OpenSSL-exception Beth Flanagan
2012-03-23 23:51 ` [PATCH 7/8] common-license: Add ICU generic Beth Flanagan
2012-03-23 23:51 ` [PATCH 8/8] setserial: Correct LICENSE Beth Flanagan
2012-03-25 10:10 ` Richard Purdie [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=1332670230.28414.70.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox