From: Alexander Kanavin <alex.kanavin@gmail.com>
Date: Wed, 23 Jan 2019 16:17:35 +0000 (+0100)
Subject: sstate.bbclass: make sure changes to SSTATE_SCAN_FILES are not ignored
X-Git-Tag: uninative-2.4~550
X-Git-Url: https://code.ossystems.io/gitweb?a=commitdiff_plain;h=ea3526961920a229e0bb5fb459952be89fce2255;p=openembedded-core.git

sstate.bbclass: make sure changes to SSTATE_SCAN_FILES are not ignored

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>
---

diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index 2f0bbd2d7d..6f51d9c187 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes/sstate.bbclass
@@ -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"