From: Joshua Watt <jpewhacker@gmail.com>
To: bitbake-devel@lists.openembedded.org
Subject: [RFC] Respect force flag in runall and runonly
Date: Tue, 27 Mar 2018 13:34:26 -0500 [thread overview]
Message-ID: <20180327183427.13983-1-JPEWhacker@gmail.com> (raw)
Implements the ability to run bitbake commands like:
$ bitbake -f --runall fetch core-image-mimimal
$ bitbake -f --runonly fetch core-image-minimal
which will invalidate the stamps for all affected tasks forcing them to
run even if they have already.
I've found this useful in a few circumstances. Most recently, I was
attempting to do A/B performance comparison of so package QA checks, so
it was pretty easy to figure out the impact of various QA checks with:
$ time bitbake -f --runall package_qa core-image-minimal
Additionally, I currently do a number of actions like this (because we
don't have runall):
$ bitbake -g <image>
$ xargs -a pn-buildlist bitbake -f -c <action>
And I would like to replace them with
$ bitbake -f --runall <action> <image>
Is this something that is even necessary/wanted?
next reply other threads:[~2018-03-27 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 18:34 Joshua Watt [this message]
2018-03-27 18:34 ` [RFC] bitbake: respect force flag in runall and runonly Joshua Watt
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=20180327183427.13983-1-JPEWhacker@gmail.com \
--to=jpewhacker@gmail.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