]> code.ossystems Code Review - openembedded-core.git/commitdiff
sstate.bbclass: make sure changes to SSTATE_SCAN_FILES are not ignored
authorAlexander Kanavin <alex.kanavin@gmail.com>
Wed, 23 Jan 2019 16:17:35 +0000 (17:17 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 24 Jan 2019 12:55:14 +0000 (12:55 +0000)
When changing the SSTATE_SCAN_FILES variable in a recipe it doesn't cause a rebuild,
so if there's a sstate-cache available with "bad" sstate data in it that will still
be used even though the recipe is updated to address this.

[YOCTO #13144]

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/classes/sstate.bbclass

index 2f0bbd2d7dfe2d19c725e71dab41e4d6716fc80a..6f51d9c1879d86c4a4e57da8185e8e527100abd7 100644 (file)
@@ -62,6 +62,7 @@ SSTATE_ARCHS = " \
 SSTATE_MANMACH ?= "${SSTATE_PKGARCH}"
 
 SSTATECREATEFUNCS = "sstate_hardcode_path"
+SSTATECREATEFUNCS[vardeps] = "SSTATE_SCAN_FILES"
 SSTATEPOSTCREATEFUNCS = ""
 SSTATEPREINSTFUNCS = ""
 SSTATEPOSTUNPACKFUNCS = "sstate_hardcode_path_unpack"