From: Foinel <flocirel@gmail.com>
To: poky@yoctoproject.org
Subject: Re: gnutls-2.12.14-r3.1 - strange rpm names yocto
Date: Wed, 14 Dec 2011 12:54:45 +0200 [thread overview]
Message-ID: <CANdftmOEcHMDp6skHttwz=t65-1o0tY3jBR2tmxLpHmvQWKv_A@mail.gmail.com> (raw)
In-Reply-To: <1323789817.25336.1.camel@ted>
Hi, I think I've narrowed the problem down to wpa-supplicant.
If you look into wpa-supplicant-0.7.3/defconfig-gnutls you can see
there CONFIG_GNUTLS_EXTRA=y. Commenting out this CONFIG_GNUTLS_EXTRA=y
creates a build into which I do not have anymore the libraries from
the -extra rpm.
On Tue, Dec 13, 2011 at 5:23 PM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> On Tue, 2011-12-13 at 12:22 +0200, Foinel wrote:
>> Looking at gnutls-2.12.14/libextra/COPYING it says just GPLv3, so no
>> dual licensing or exceptions of any kind for these extra libraries.
>> Can anyone explain why in
>> meta/conf/distro/include/default-distrovars.inc it says:
>>
>> # This is a list of packages that are used by the build system to
>> build the distribution, they are not
>> # directly part of the distribution..
>> HOSTTOOLS_WHITELIST_GPLv3 ?= ""
>> WHITELIST_GPLv3 ?= "less"
>> LGPLv2_WHITELIST_GPLv3 ?= "libassuan gnutls libtasn1 libidn libgcc gcc-runtime"
>>
>> Does this mean gnutls is some sort of a host tool?
>> Because of this fact (gnutls being in LGPLv2_WHITELIST_GPLv3), then
>> the restriction to avoid GPLv3 packages seems not applicable to
>> gnutls. Does anyone know if gnutls is a special case in what concerns
>> the licensing?
>
> I think we were only including GPLv2 pieces of gnutls in most images. If
> something is now pulling in the -extras package, we have a problem. It
> sounds like we should remove it from the whitelist.
>
> Cheers,
>
> Richard
>
next prev parent reply other threads:[~2011-12-14 10:54 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
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 [this message]
-- 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='CANdftmOEcHMDp6skHttwz=t65-1o0tY3jBR2tmxLpHmvQWKv_A@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.