From: Saul Wold <saul.wold@intel.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [poky] libcdaudio license issue
Date: Mon, 06 Dec 2010 18:38:15 -0800 [thread overview]
Message-ID: <4CFD9E17.5070209@intel.com> (raw)
In-Reply-To: <20101206225236.GD29253@denix.org>
On 12/06/2010 02:52 PM, Denys Dmytriyenko wrote:
> On Mon, Dec 06, 2010 at 02:50:10PM -0800, Saul Wold wrote:
>> On 12/06/2010 11:48 AM, Frans Meulenbroeks wrote:
>>> I was checking libcdaudio for LICENSE info.
>>> recipe says GPL
>>> COPYING file is the GPLv2 one
>>> README file says:
>>>
>>> libcdaudio is distributed under the GNU Library General Public
>>> License, included in this package under the top level source directory
>>> in the file COPYING
>>>
>>> C files also mention LGPL. but say v2 or later
>>>
>>> What to do with this in the LICENSE field? LGPLv2+ ?
>>>
>> This seems reasonable, you should also include the header chunk in the
>> LIC_FILES_CHKSUM, you can specify start and end lines for the checksum.
>
> Saul,
>
> We don't have this feature in OpenEmbedded yet... But it would be nice to port
> it from Poky though! :)
>
Denys, sorry I saw this via my poky email and did not notice it was OE
also, I will what what I cross post next time!
Glad to hear that you like the idea! We will have all Poky recipes
checksummed this week!
Sau!
next prev parent reply other threads:[~2010-12-07 2:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 19:48 libcdaudio license issue Frans Meulenbroeks
2010-12-06 20:15 ` Maupin, Chase
2010-12-06 20:30 ` Denys Dmytriyenko
2010-12-06 22:50 ` [poky] " Saul Wold
2010-12-06 22:52 ` Denys Dmytriyenko
2010-12-07 2:38 ` Saul Wold [this message]
2010-12-07 9:23 ` Frans Meulenbroeks
2010-12-08 23:25 ` Saul Wold
2010-12-07 22:03 ` Scott Garman
2010-12-07 22:31 ` Frans Meulenbroeks
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=4CFD9E17.5070209@intel.com \
--to=saul.wold@intel.com \
--cc=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=poky@yoctoproject.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