From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>,
Peter Seebach <peter.seebach@windriver.com>,
Jeff Polk <jeff.polk@windriver.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] cooker.py: Remove explicit build targets from the ignored list
Date: Fri, 31 May 2013 08:29:43 +0100 [thread overview]
Message-ID: <1369985383.14887.341.camel@ted> (raw)
In-Reply-To: <1369799698-1417-1-git-send-email-mark.hatle@windriver.com>
On Tue, 2013-05-28 at 22:54 -0500, Mark Hatle wrote:
> From: Peter Seebach <peter.seebach@windriver.com>
>
> If something is in ASSUMED_PROVIDED, and a user tries to build it
> explicitly, Nothing Happens. Bitbake just says it ran 0 out of 0
> tasks. No diagnostics or explanations are offered.
>
> In practice, the right thing is probably to assume that explicit
> targets are intentional. So far as I can tell, cooker.buildTargets
> is called only from the command line or from command.py, and both
> cases seem to be explicit user actions.
>
> Signed-off-by: Peter Seebach <peter.seebach@windriver.com>
> Signed-off-by: Jeff Polk <jeff.polk@windriver.com>
>
> Rename 'status' to 'recipecache' to match recent changes.
>
> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
> ---
> lib/bb/cooker.py | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/lib/bb/cooker.py b/lib/bb/cooker.py
> index 2ae3e9d..8f0e90c 100644
> --- a/lib/bb/cooker.py
> +++ b/lib/bb/cooker.py
> @@ -1067,6 +1067,11 @@ class BBCooker:
> universe = ('universe' in targets)
> targets = self.checkPackages(targets)
>
> + # Explicitly disignore things that have been requested.
> + for target in targets:
> + if target in self.recipecache.ignored_dependencies:
> + self.recipecache.ignored_dependencies.remove(target)
> +
> def buildTargetsIdle(server, rq, abort):
> if abort or self.state == state.stop:
> rq.finish_runqueue(True)
I'm not sure this is the right thing to do, the reason being
determinism. I don't expect different results for X in the different
cases:
bitbake X Y
bitbake X
(assuming Y is ASSUME_PROVIDED)
For example, X will rebuild between these two commands since the sstate
and task checksums will be different between the two. This really needs
more thought to make a consistent user experience...
Cheers,
Richard
next prev parent reply other threads:[~2013-05-31 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 3:54 [PATCH] cooker.py: Remove explicit build targets from the ignored list Mark Hatle
2013-05-31 7:29 ` Richard Purdie [this message]
2013-05-31 10:54 ` Paul Eggleton
2013-05-31 16:32 ` Peter Seebach
2013-06-04 10:33 ` Richard Purdie
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=1369985383.14887.341.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=jeff.polk@windriver.com \
--cc=mark.hatle@windriver.com \
--cc=peter.seebach@windriver.com \
/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.