linux/poky.git/meta/classes/sstate.bbclass, branch yocto-4.0.29

do_package/sstate/sstatesig: Change timestamp clamping to hash output only

2024-12-09T15:54:03+00:00

The code was changing the timestamps of the files in the do_package output, particularly the files added for debug sources. This was to do two things: a) make do_package sstate more reproducible b) ensure better hash equivalence matching Unfortuately the debug source files are hardlinks into the source tree for efficiency so touching these, touches a lot of files in ${B} and ${S}. This causes unpredictable effects if compile is run again for example, or could cause compiling in the install task. The hash equivalence matching is of key importance but we can mimic that using clamping of the file timestamps in the depsig output used to generate the hashes. This patch drops the global timestamp clamping, instead allowing the files to retain their creation timestamps into sstate. This makes do_package sstate slightly less reproducibile. We could clamp the sstate timestamps but that would lead to two different sets of timestamps depending on whether the data came from sstate or not. I'd prefer to have consistent code behaviour, rather than differing behavhour depending on whether data came from sstate or not. If we wanted to have reproducibiliy and fix the "corruption" of S/B and have consistent codepaths, the only other option would be two copies of the sources, which could end up huge and seems the least desireable option. This patch therefore drops the timestamp clamping in the sstate files and tweaks the depsig data generation to clamp the timestamps for do_package instead since this seems the best compromise. I validated that rpm/deb/ipk files still generate correctly as before. (From OE-Core rev: 0c93bb692b39af51f0ca109dfd1f949abe7eea9c) Signed-off-by: Richard Purdie (cherry picked from commit 475759fdab7200488b2a568b2ba1aa31a456d113) Signed-off-by: Steve Sakoman

buildhistory: Simplify intercept call sites and drop SSTATEPOSTINSTFUNC usage

2024-09-27T12:57:35+00:00

We planned to drop SSTATEPOSTINSTFUNC some time ago with the introduction of postfuncs. Finally get around to doing that which should make the buildhistory code a little more readable. Unfortunately ordering the buildhistory function calls after the sstate ones is difficult without coding that into the sstate class. This patch does that to ensure everything functions as expected until we can find a better way. This is still likely preferable than the generic sstate postfuncs support since the function flow is much more readable. (From OE-Core rev: 78ca086441b21dedd9c471a3d3200c24fd9ec8d2) Signed-off-by: Richard Purdie (cherry picked from commit c9e2a8fa2f0305ef1247ec405555612326f798f8) Signed-off-by: Steve Sakoman

sstate: Allow optimisation of do_deploy_archives task dependencies

2022-12-01T19:35:05+00:00

do_deploy_archives tasks don't need their dependencies so we can optimistion this as we do for some other tasks. (From OE-Core rev: 1e32ad0849f06aee92fe844e8eaee73c5935bfb0) Signed-off-by: Jose Quaresma Signed-off-by: Alexandre Belloni (cherry picked from commit 3dd9f6e398844380d3765c54d35afe0d2ccf82e7) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

abi_version/sstate: Bump hashequiv and sstate versions due to git changes

2022-05-12T15:44:06+00:00

The autobuilder sstate was corrupted via incorrect equiavlences caused by the security fix to git and the poor interaction that had with SCM version checks under fakeroot/pseudo. Bump the versions to enable a clean slate to work off. (From OE-Core rev: 69f2d0822462e77d09b4781dcec41a0747e4d387) Signed-off-by: Richard Purdie Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie (cherry picked from commit 3b6672730372e130d4d72b683fc3150911964745) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

sstate: Allow optimisation of do_create_spdx task dependencies

2022-03-16T10:31:41+00:00

do_create_spdx tasks don't need their dependencies so we can optimistion this as we do for some other tasks. (From OE-Core rev: 6723a045c3a46537bb76111f8306b5960e532522) Signed-off-by: Richard Purdie

meta/scripts: Improve internal variable naming

2022-03-10T08:00:28+00:00

Update internal variable names to improve the terms used. (From OE-Core rev: f408068e5d7998ae165f3002e51bc54b380b8099) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

sstate: inside the threadedpool don't write to the shared localdata

2022-03-07T22:44:55+00:00

When inside the threadedpool we make a copy of the localdata to avoid some race condition, so we need to use this new localdata2 and stop write the shared localdata. (From OE-Core rev: 1fa763b2022822a76fde541724e83e1977833d03) Signed-off-by: Jose Quaresma Signed-off-by: Richard Purdie

sstate: do not add TARGET_ARCH to pkgarch for cross recipes.

2022-03-02T18:43:24+00:00

This is redundant (target arch is already in PN), and breaks compiling a cross-canadian toolchain, as that needs populating the sysroot with two different native-hosted toolchains built from cross recipes. Inserting TARGET_ARCH allows only one or the other. (From OE-Core rev: 33fc1792cd782feb8dbb4285e3006bb588f7978f) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

meta/scripts: Automated conversion of OE renamed variables

2022-02-21T23:37:27+00:00

(From OE-Core rev: aa52af4518604b5bf13f3c5e885113bf868d6c81) Signed-off-by: Richard Purdie

sstate: Setup fetcher environment in advance

2022-02-20T16:45:25+00:00

The threading code here can race as the fetcher changes the environment which is shared between the threads. By setting it up in advance, it isn't changed and therefore no longer races. (From OE-Core rev: cabc3cc2eac5916e63340c18d1074411b377ced4) Signed-off-by: Richard Purdie