From: Foinel <flocirel@gmail.com>
To: poky@yoctoproject.org
Subject: Re: gnutls-2.12.14-r3.1 - strange rpm names yocto
Date: Tue, 13 Dec 2011 11:18:22 +0200 [thread overview]
Message-ID: <CANdftmPXu-zrbaha3Gc5bP7=cZX29bqe8Nw2437XTgeEqJacQw@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1srCZg4-S-4EPsbCifk7Kr=SuDvsoqX0ww9p8WGdy=53Fg@mail.gmail.com>
So for example, in the situation when I have a build from which I want
to exclude GPLv3 code from, but gnutls is added to the build as a
dependency of some package, and the licensing of gnutls is as follows:
LICENSE = "GPLv3+ & LGPLv2.1+"
LICENSE_${PN} = "LGPLv2.1+"
LICENSE_${PN}-xx = "LGPLv2.1+"
LICENSE_${PN}-bin = "GPLv3+"
LICENSE_${PN}-extra = "GPLv3+"
LICENSE_${PN}-openssl = "GPLv3+"
then my understanding is either don't include any code from gnutls as
it's double licence or just include the non GPLv3 rpms (the first and
second rpm). Am I right?
On Tue, Dec 13, 2011 at 1:21 AM, Khem Raj <raj.khem@gmail.com> wrote:
> On Mon, Dec 12, 2011 at 2:42 PM, Andrei Gherzan <andrei@gherzan.ro> wrote:
>> So as you can see here is checked every package. This variable,
>> LGPLv2_WHITELIST_GPLv3, is defined in default-distrovars.inc as:
>> LGPLv2_WHITELIST_GPLv3 ?= "libassuan gnutls libtasn1 libidn libgcc
>> gcc-runtime"
>
> most of them have exceptions along with gplv3 or are lgplv3/lgplv2.1
> e.g. the gcc bits in there are gplv3 with GCC Runtime Library Exception
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
next prev parent reply other threads:[~2011-12-13 9:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 10:58 gnutls-2.12.14-r3.1 - strange rpm names yocto Foinel
2011-12-11 16:10 ` Andrei Gherzan
2011-12-11 22:12 ` Richard Purdie
2011-12-12 14:54 ` Foinel
2011-12-12 22:42 ` Andrei Gherzan
2011-12-12 23:21 ` Khem Raj
2011-12-13 9:18 ` Foinel [this message]
2011-12-13 9:40 ` Anders Darander
2011-12-13 10:04 ` Foinel
2011-12-13 19:52 ` Khem Raj
2011-12-14 7:26 ` Andrei Gherzan
2011-12-13 10:22 ` Foinel
2011-12-13 15:23 ` Richard Purdie
2011-12-14 10:54 ` Foinel
-- strict thread matches above, loose matches on Subject: below --
2011-12-09 22:15 Andrei Gherzan
2011-12-09 23:35 ` Joshua Lock
2011-12-10 0:02 ` Andrei Gherzan
2011-12-10 4:08 ` Mark Hatle
2011-12-11 9:48 ` Richard Purdie
2011-12-19 14:05 ` Andrei Gherzan
2011-12-19 17:29 ` Saul Wold
2011-12-20 11:09 ` Andrei Gherzan
2011-12-20 18:18 ` Saul Wold
2011-12-20 23:41 ` Andrei Gherzan
2011-12-21 5:55 ` Saul Wold
2011-12-21 9:47 ` Andrei Gherzan
2011-12-21 18:54 ` Andrei Gherzan
2011-12-21 20:23 ` Andrei Gherzan
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='CANdftmPXu-zrbaha3Gc5bP7=cZX29bqe8Nw2437XTgeEqJacQw@mail.gmail.com' \
--to=flocirel@gmail.com \
--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.