summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools
diff options
context:
space:
mode:
authorMichael Ho <Michael.Ho@bmw.de>2019-05-27 17:42:36 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-05-30 12:34:56 +0100
commitfdc000b8ae1577f1b29efb2cc4927664ad41e21c (patch)
tree9709ec79338d41e70046aca3d401fb4efb3d578f /meta/recipes-devtools
parentbd59536158ba29aec979378068d5d50b4a29282d (diff)
downloadopenembedded-core-contrib-fdc000b8ae1577f1b29efb2cc4927664ad41e21c.tar.gz
base.bbclass: add named SRCREVs to the sstate hash
Several fetchers support named sources that require setting a SRCREV with the source name as a suffix. These named SRCREV variables are not captured in the sstate hash calculation because they're only referenced within the bitbake fetcher function. Several recipes avoid this bug by adding the different SRCREVs to their packaging versioning but this is not enforced so it is very trivial to trip this bug case. Add a snippet to the base.bbclass anonymous python to add all named SRCREV variables to the vardeps of do_fetch to capture them in the sstate hash calculation. Testing of the bug can be shown by running the following bitbake commands with this patch set not applied: bitbake vulkan-demos | tee sed -i 's/SRCREV_gli = ".*"/SRCREV_gli = "xxx"/' \ ../meta/recipes-graphics/vulkan/vulkan-demos_git.bb bitbake vulkan-demos | tee; The above results in no errors despite a broken SRCREV because the recipe is considered unchanged by the bitbake sstate hash. After applying this patch the above commands instead result in a fetcher error which is correct. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools')
0 files changed, 0 insertions, 0 deletions