From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 0/1] QA check for defined packages
Date: Wed, 12 Oct 2011 10:44:29 -0700 [thread overview]
Message-ID: <4E95D1FD.3020608@linux.intel.com> (raw)
In-Reply-To: <1318423185.23801.153.camel@ted>
On 10/12/2011 05:39 AM, Richard Purdie wrote:
> On Tue, 2011-10-11 at 15:29 -0700, Joshua Lock wrote:
>> Folks,
>>
>> I'm looking for some comments on this WIP patch.
>>
>> The reason I've added this is because the hob GUI requires us to offer much
>> more reliable metadata - we show the user available packages, as defined by
>> each recipe, to add to their image. Should a recipe define a package and yet
>> not actually create it and the user has included that in their image we cause
>> errors at build time.
>>
>> However whilst the idea seems sound enough, there are some caveats - running
>> a world build with this patch I see failures fairly early on at least a few
>> of which I'd expect we'll need to special-case:
>> * eglibc-local
>> * linux-yocto
>> * linux-libc-headers
>> * gcc-runtime
>
> You'd probably get much better results from this patch if you account
> for ALLOW_EMPTY_<pkgname> btw...
Indeed, that does look useful.
So, ignoring the Hob discussion I still think this QA check will be
generally useful. Are others open to this if I work on it further?
Regards,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
prev parent reply other threads:[~2011-10-12 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 22:29 [RFC PATCH 0/1] QA check for defined packages Joshua Lock
2011-10-11 22:29 ` [RFC PATCH 1/1] insane.bbclass: add qa check to ensure declared packages exist Joshua Lock
2011-10-12 12:37 ` [RFC PATCH 0/1] QA check for defined packages Richard Purdie
2011-10-12 12:40 ` Koen Kooi
2011-10-12 17:43 ` Joshua Lock
2011-10-12 19:18 ` Richard Purdie
2011-10-12 19:23 ` Joshua Lock
2011-10-12 12:39 ` Richard Purdie
2011-10-12 17:44 ` Joshua Lock [this message]
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=4E95D1FD.3020608@linux.intel.com \
--to=josh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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