From: Peter Seebach <peter.seebach@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/1] cooker.py: disignore explicitly requested packages
Date: Wed, 8 Aug 2012 18:19:41 -0500 [thread overview]
Message-ID: <cover.1344467794.git.peter.seebach@windriver.com> (raw)
It turns out that ASSUMED_PROVIDED trumps command-line. This is surprising,
and more so because there is no diagnostic; the user is not told "this
package is being ignored", you just get told that 0 out of 0 tasks were
run, and all succeeded. We could add a diagnostic, but really, it seems as
though it makes sense to trust the user; a user who really wants to build
bzip2-native even though it is presumably provided by the host probably has
reasons. (Note: "The test plan says..." is a reason.)
The following changes since commit 23bd5300b4a99218a15f4f6b0ab4091d63a602a5:
Richard Purdie (1):
data_smart: Fix unanchored regexp causing strange parsing issue
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/cooker
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/cooker
Peter Seebach (1):
cooker.py: Remove explicit build targets from the ignored list
lib/bb/cooker.py | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
next reply other threads:[~2012-08-08 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 23:19 Peter Seebach [this message]
2012-08-08 23:19 ` [PATCH 1/1] cooker.py: Remove explicit build targets from the ignored list Peter Seebach
2012-08-09 17:30 ` Paul Eggleton
2012-08-09 17:44 ` Peter Seebach
2012-08-09 17:54 ` Chris Larson
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=cover.1344467794.git.peter.seebach@windriver.com \
--to=peter.seebach@windriver.com \
--cc=bitbake-devel@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