From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: poky@yoctoproject.org
Subject: Re: [oe] libcdaudio license issue
Date: Mon, 06 Dec 2010 15:30:48 -0500 [thread overview]
Message-ID: <20101206203048.GA29253@denix.org> (raw)
In-Reply-To: <AANLkTi==kWiyOrmeUeUVNeC8FT0B8XxruHA0X4qMaPs_@mail.gmail.com>
On Mon, Dec 06, 2010 at 08:48:28PM +0100, 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+ ?
Frans,
I'd agree that LGPLv2+ is a safe bet, especially since that's what is
specified in the sources.
--
Denys
WARNING: multiple messages have this Message-ID (diff)
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: poky@yoctoproject.org
Subject: Re: libcdaudio license issue
Date: Mon, 06 Dec 2010 15:30:48 -0500 [thread overview]
Message-ID: <20101206203048.GA29253@denix.org> (raw)
In-Reply-To: <AANLkTi==kWiyOrmeUeUVNeC8FT0B8XxruHA0X4qMaPs_@mail.gmail.com>
On Mon, Dec 06, 2010 at 08:48:28PM +0100, 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+ ?
Frans,
I'd agree that LGPLv2+ is a safe bet, especially since that's what is
specified in the sources.
--
Denys
next prev parent reply other threads:[~2010-12-06 20:31 UTC|newest]
Thread overview: 16+ 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 [this message]
2010-12-06 20:30 ` Denys Dmytriyenko
2010-12-06 22:50 ` Saul Wold
2010-12-06 22:50 ` [poky] " Saul Wold
2010-12-06 22:52 ` [oe] " Denys Dmytriyenko
2010-12-06 22:52 ` [poky] " Denys Dmytriyenko
2010-12-07 2:38 ` [oe] " Saul Wold
2010-12-07 2:38 ` [poky] " Saul Wold
2010-12-07 9:23 ` [oe] " Frans Meulenbroeks
2010-12-07 9:23 ` [poky] " Frans Meulenbroeks
2010-12-08 23:25 ` Saul Wold
2010-12-09 0:47 ` [oe] " 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=20101206203048.GA29253@denix.org \
--to=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 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.