From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Martin Jansa <martin.jansa@gmail.com>
Subject: Re: [PATCH] base.bbclass: add cleansstate task between clean and cleanall
Date: Thu, 02 Jun 2011 22:43:11 -0700 [thread overview]
Message-ID: <4DE8746F.2000100@linux.intel.com> (raw)
In-Reply-To: <1307040964-11468-1-git-send-email-Martin.Jansa@gmail.com>
On 06/02/2011 11:56 AM, Martin Jansa wrote:
> * sometimes it's usefull to remove only sstate cache and keep downloaded sources for rebuild
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> meta/classes/base.bbclass | 7 +++++--
> 1 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
> index 8f4ef1e..6f0484e 100644
> --- a/meta/classes/base.bbclass
> +++ b/meta/classes/base.bbclass
> @@ -408,10 +408,13 @@ def check_gcc3(data):
>
> return False
>
> -addtask cleanall after do_clean
> -python do_cleanall() {
> +addtask cleansstate after do_clean
> +python do_cleansstate() {
> sstate_clean_cachefiles(d)
> +}
>
> +addtask cleanall after do_cleansstate
> +python do_cleanall() {
> src_uri = (bb.data.getVar('SRC_URI', d, True) or "").split()
> if len(src_uri) == 0:
> return
I do this _a lot_ manually. This would take some of the guesswork and
lazy wildcard usage deleting more than is necessary. Is there any
documentation necessary to make it clear how this new clean directive
would be used? I know there is some resistance to adding additional
clean variants - some docs might help assuage that?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-06-03 5:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 18:56 [PATCH] base.bbclass: add cleansstate task between clean and cleanall Martin Jansa
2011-06-02 19:19 ` Koen Kooi
2011-06-02 21:51 ` Khem Raj
2011-06-03 5:43 ` Darren Hart [this message]
2011-06-06 17:06 ` Saul Wold
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=4DE8746F.2000100@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=martin.jansa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox