All of lore.kernel.org
 help / color / mirror / Atom feed
From: Foinel <flocirel@gmail.com>
To: poky@yoctoproject.org
Subject: Re: gnutls-2.12.14-r3.1 - strange rpm names yocto
Date: Mon, 12 Dec 2011 16:54:12 +0200	[thread overview]
Message-ID: <CANdftmPSkw9fEcucJcZPLm4kFticM6t7-pe4HUZoRxgsuj8t0w@mail.gmail.com> (raw)
In-Reply-To: <1323641532.2731.5.camel@ted>

Hi,I am experiencing this issue on a new build from scratch configured
toexclude GPLv3 packages/files. I do not have gnutls added to any
.bbtasks file, it gets added as a dependency of some package(s) I
ambuilding.So I would have 2 issues here: first, after the build
completes, I getthe GPLv3 libraries from the -extra rpm into the
rootfs; second, howcan I get a view of all the packages that drag
gnutls into the build?(I don't think that looking into each *.bb for
the dependency is veryuseful; is there any file in which I can find
some sort of adependency tree for all the packages I am
building?)Thanks.
On Mon, Dec 12, 2011 at 12:12 AM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> On Sun, 2011-12-11 at 18:10 +0200, Andrei Gherzan wrote:
>> I tried something else today.
>>
>> I created from scratch a new image-minimal and i added wpa-supplicant to
>> IMAGE_INSTALL - rpm's names are wpa-supplicant-[stuff]. After finishing
>> this image i could see that gnutls-extra is again in rootfs even if i
>> excluded GPLv3 from build. After searching a little i could see that
>> gnutls is a dependency for wpa-supplicant and, in the generated gnutls
>> spec, that gnutls-extra is required by gnutls-bin.
>>
>> If bin requires extra than this build should have ended with an error...
>> no provider as GPLv3 excluded. Am i right?
>
> Are you running a build which includes GPLv3, then running a build
> excluding GPLv3? I suspect doing that could confuse the system a little
> but I'm not sure exactly what the issue would be.
>
> If on the other hand you always exclude GPLv3 from a given build
> directory, there shouldn't be any way for it to become contaminated.
>
> There are various changes in master which are working towards making the
> license checking a build and runtime check rather than the build time
> check in 1.1.
>
> Cheers,
>
> Richard
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky


  reply	other threads:[~2011-12-12 14: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 [this message]
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
  -- 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=CANdftmPSkw9fEcucJcZPLm4kFticM6t7-pe4HUZoRxgsuj8t0w@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.