public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
To: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	Anton Mikanovich <amikan@ilbers.de>
Subject: RE: [PATCH] sstate: add cleansstate task
Date: Thu, 13 Jan 2022 13:50:51 +0000	[thread overview]
Message-ID: <AS4PR10MB5318C0320CE50A9E588BD921ED539@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <359a3ae8-30d1-df26-eeb9-e6f09c5e0634@siemens.com>

Kiszka, Jan, Mittwoch, 12. Januar 2022 15:02:
> 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.

Agreed.
I missed that in my initial implementation, and would call it a bug...

Adriaan



  reply	other threads:[~2022-01-13 13:50 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
2022-01-13 13:50   ` Schmidt, Adriaan [this message]
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=AS4PR10MB5318C0320CE50A9E588BD921ED539@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM \
    --to=adriaan.schmidt@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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