From: Peter Seebach <peter.seebach@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] sanity.bbclass: Check for bogus values in BBCLASSEXTEND
Date: Wed, 9 May 2012 16:09:26 -0500 [thread overview]
Message-ID: <20120509160926.2e297150@wrlaptop> (raw)
In-Reply-To: <1336597189.2494.80.camel@ted>
On Wed, 9 May 2012 21:59:49 +0100
Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> FWIW, this isn't going to work. Its checking the sanity in
> "configuration" space, pre recipe parse so it won't pick up on the
> errors we want it to.
>
> So whilst its well intentioned, it isn't going to work as designed and
> we'll have to rethink it. I can't think of a good way to fix it right
> now, we don't really have a structure for recipe checks at this point.
Oh, that has to be per-recipe? I thought BBCLASSEXTEND was top-level.
Adding recipe checks of some sort seems useful, but that is a bigger
project, so I guess we can drop that. Note that this was in sgw's
consolidated pull request, too.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2012-05-09 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 1:45 v4 or so [PATCH 0/3] sanity.bbclass and friends: toolchain sanity Peter Seebach
2012-05-02 1:45 ` [PATCH 1/3] conf/machine: Clean up configuration values Peter Seebach
2012-05-02 1:45 ` [PATCH 2/3] sanity.bbclass: Implement initial toolchain sanity checks Peter Seebach
2012-05-02 1:45 ` [PATCH 3/3] sanity.bbclass: Check for bogus values in BBCLASSEXTEND Peter Seebach
2012-05-09 20:59 ` Richard Purdie
2012-05-09 21:09 ` Peter Seebach [this message]
2012-05-09 23:32 ` v4 or so [PATCH 0/3] sanity.bbclass and friends: toolchain sanity Saul Wold
2012-05-09 23:58 ` Peter Seebach
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=20120509160926.2e297150@wrlaptop \
--to=peter.seebach@windriver.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 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.