We have a shared sstate-cache that is populated by us building nightly images for various branches using Jenkins. This cache is pruned periodically (with special care of the siginfo files since we don't have 80b3974081c4a8c604e23982a6db8fb32c616058 yet.)
Recently we went back to one of those branches that hadn't been changed for a while and were surprised to find that Bitbake wanted to build loads of packages from source. It turned out that whilst the populate_sysroot.gz and package_ipk.tgz files were still in the sstate-cache, the package.tgz tarball was not. This meant that the whole package was built again in order to satisfy the build dependencies of other packages that had changed. I'm suspicious that this behaviour was introduced by the optimisation in a0f584ac3d5a94dec121b684206ecd40c968f7fc so we hadn't seen it on older branches. Is there a way to cause the package.tgz file to be touched during these nightly builds too? Or, is there a way to get hold of the complete set of sstate files so they can be touched all in one go? Thanks. Mike. -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
