From: Jan Kiszka <jan.kiszka@siemens.com>
To: Adriaan Schmidt <adriaan.schmidt@siemens.com>,
<isar-users@googlegroups.com>,
Anton Mikanovich <amikan@ilbers.de>
Subject: Re: [PATCH] sstate: add cleansstate task
Date: Wed, 12 Jan 2022 15:01:42 +0100 [thread overview]
Message-ID: <359a3ae8-30d1-df26-eeb9-e6f09c5e0634@siemens.com> (raw)
In-Reply-To: <20220107081624.1323440-1-adriaan.schmidt@siemens.com>
On 07.01.22 09:16, Adriaan Schmidt wrote:
> This adds the sstate cleanup task known from OE.
>
> Signed-off-by: Adriaan Schmidt <adriaan.schmidt@siemens.com>
> ---
> meta/classes/base.bbclass | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
> index d8347b9..a728211 100644
> --- a/meta/classes/base.bbclass
> +++ b/meta/classes/base.bbclass
> @@ -237,7 +237,13 @@ python do_clean() {
> }
>
> # Derived from OpenEmbedded Core: meta/classes/base.bbclass
> -addtask cleanall after do_clean
> +addtask cleansstate after do_clean
> +do_cleansstate[nostamp] = "1"
> +python do_cleansstate() {
> + sstate_clean_cachefiles(d)
> +}
> +
> +addtask cleanall after do_cleansstate
> do_cleanall[nostamp] = "1"
> python do_cleanall() {
> src_uri = (d.getVar('SRC_URI', True) or "").split()
I would vote for making this a 0.8 feature, given that sstate is merged
already and default-on. Too many case required purging me the complete
sstate already, though only a single recipe would have been sufficient.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-01-12 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 8:16 Adriaan Schmidt
2022-01-12 14:01 ` Jan Kiszka [this message]
2022-01-13 13:50 ` Schmidt, Adriaan
2022-01-17 6:06 ` Anton Mikanovich
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=359a3ae8-30d1-df26-eeb9-e6f09c5e0634@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox