From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH 0/1] QA check for defined packages
Date: Wed, 12 Oct 2011 13:39:37 +0100 [thread overview]
Message-ID: <1318423185.23801.153.camel@ted> (raw)
In-Reply-To: <cover.1318371066.git.josh@linux.intel.com>
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...
Cheers,
Richard
next prev parent reply other threads:[~2011-10-12 12:45 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 [this message]
2011-10-12 17:44 ` Joshua Lock
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=1318423185.23801.153.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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 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.