On Mon, 2016-01-25 at 10:47 -0500, Bruce Ashfield wrote: > On 2016-01-25 10:07 AM, Richard Purdie wrote: > > If we don't do this, the deploy sstate object contains an every > > increasing number of modules tarballs and kernel images, one per > > execution of "-c deploy -f". > > > > Stupid question, since my sstate/deploy foo is weak at times. > Does this mean that only a single set of modules + kernel images > will be in tmp/deploy ? Or is it only sstate that is being > cleaned ?
One side effect is that it will remove the older copies. The older copies were being built into each new sstate object which was growing huge. > I sometimes need multiple copies around for debug purposes, so > I'm wondering if that is still possible with this change ? You'd need to archive them before running another build since this effectively cleans up the older copies now. This is due to the system removing the old sstate "object", then installing a new one to replace it. You can't keep the old ones around easily as they're named to conflict (and hence replace each other). Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
