There is a caveat here. This will touch all sstate that is needed to construct an image, but won't touch sstate needed to build components that go into the image. So target packages are guaranteed to be kept, but native items may be deleted - I've seen this with e.g. java compiler that is used for few specific, rarely changing items.
Alex On Thu, 18 Nov 2021 at 12:11, Ross Burton <[email protected]> wrote: > If you can say that you've touched all the sstate you'll need then the > find trick is sufficient. I use it on our CI to prune any sstate that > hasn't been touched in a month, for example. > > The script is more powerful and can selectively save or destroy > things, but can potentially be more complicated than just nuking > anything old. > > Ross > > On Thu, 18 Nov 2021 at 10:38, Robert P. J. Day <[email protected]> > wrote: > > > > > > assuming my (correct) understanding of sstate-cache is that, as time > > goes by, it just gets larger and larger, it will increasingly contain > > content that is of little value anymore, what is the simplest way to > > purge or prune entries that are no longer involved in any desired > > builds? > > > > i'm guessing a simple way to do that is to first delete tmp/, then > > build any current targets/images, immediately followed by something > > like: > > > > $ find sstate-cache -type f -atime +1 -delete > > > > is there anything fancier than that? > > > > rday > > > > > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#158475): https://lists.openembedded.org/g/openembedded-core/message/158475 Mute This Topic: https://lists.openembedded.org/mt/87140377/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
