We save the following sstate cache files currently: packagedata.tgz packagedata.tgz.siginfo package.tgz.siginfo package.tgz populate-sysroot.tgz populate-sysroot.tgz.siginfo populate-lic.tgz.siginfo populate-lic.tgz deploy-rpm.tgz deploy-rpm.tgz.siginfo The end user only needs populate-sysroot.tgz and deploy-rpm.tgz in theory, maybe we can add a configure variable to let the user turn off the other files' generation (also turn off the .siginfo) to save the build time and disk space. We may add some variables like: (turn on all of generation by default) SSTATE_MODE[siginfo] = "0" SSTATE_MODE[packagedata] = "0" SSTATE_MODE[package] = "0" ...
The end user does at least need packagedata and populate-lic, otherwise those have to get rebuilt from scratch. The only data that is not strictly needed is package and that is required if you change package formats for example. Before we start making things configurable, I'd like to see performance numbers about the speed improvements this would give. I'm not sure its worth adding extra code paths just for one sstate target.
(In reply to comment #1) > The end user does at least need packagedata and populate-lic, otherwise > those have to get rebuilt from scratch. The only data that is not strictly > needed is package and that is required if you change package formats for > example. > > Before we start making things configurable, I'd like to see performance > numbers about the speed improvements this would give. I'm not sure its worth > adding extra code paths just for one sstate target. Hi RP, thanks for the review, it's not easy to disable the generation of these files, I will try it later to get the performance numbers.
Setting to VERIFIED as per above 2 comments. Please open a new bug if necessary.