From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/5] license.bbclass parsing changes and common-license additions
Date: Thu, 26 May 2011 14:30:42 -0700 [thread overview]
Message-ID: <1306445442.5911.9.camel@vorpal.jf.intel.com> (raw)
In-Reply-To: <4DDD90F9.5030901@intel.com>
On Wed, 2011-05-25 at 16:30 -0700, Elizabeth Flanagan wrote:
> This pull request is a consolidated pull of some changes to the license.bbclass
> license parsing, some cleanup of existing licenses, and some additions to/
> modifications of various licenses kept in meta/files/common-licenses.
>
> I've modified the common-licenses by adding licenses from the Software Package
> and Data Exchange group/OSI and using their naming convention for internal
> parsing within license.bbclass.
>
> Licenses were retrieved from http://spdx.org/licenses/ or
> in cases where text of the license was missing:
> http://opensource.linux-mirror.org/licenses/
>
> I've also modified some recipe's LICENSE field, either because the field was
> unparsable or the LICENSE was factually incorrect. This was not an entire audit
> of every LICENSE field but there were some errors that were obvious.
>
> And lastly, using python abstract syntax trees as a parser and an ast visitor
> class, I've begun the first steps to being able to put some sanity to license
> selection.
>
> One note. License modifiers have traditionally been limited to the "or greater"
> modifier "+". I've added another modifier "with exceptions" for licenses that
> have no generic ie common-licenses/GPL-2,0-with-GCC-exception
>
> The modifiers are ignored for now, but I'll be looking at the logic for them
> next.
I like the direction you are going with this. Good job. I have one minor
niggle in patch 2 of the series.
Also you could probably merge all of the license.bbclass changes into
one patch with a liberal application of git rebase -i and the fixup
flag.
Cheers,
Joshua
--
Joshua Lock
Yocto Project Build Monkey
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-05-26 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 23:30 [PATCH 0/5] license.bbclass parsing changes and common-license additions Elizabeth Flanagan
2011-05-26 21:30 ` Joshua Lock [this message]
2011-05-27 17:29 ` Richard Purdie
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=1306445442.5911.9.camel@vorpal.jf.intel.com \
--to=josh@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox