On Tuesday 30 July 2019 at 09:14:01 -0500, Mark Hatle wrote: > Richard mentioned in the bitbake-devel thread that there may be external tools > using some of the components. I'm not sure how to even identify what those > tools are at this time, but a new sstate version entry may be enough to start > to > deal with them.
We have a couple of tools that know the format of sstate cache files: The first tool[1] processes locked-sigs.inc to update the atime of any files that would be necessary for the build. (We discovered that relying on actually building to update atime was insufficient since it skipped sstate files that were only necessary in order to build others.) The second tool is simpler and just expires sstate files that haven't been accessed in a while. We have a handful of different expiry policies by PN, so we need to understand where that is in the filename. This tool needs to cope with a cache populated by a mixture of oe-core versions, so any change in format risks complicating it. Mike. [1] http://lists.openembedded.org/pipermail/openembedded-core/2016-April/120227.html -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
