From ea3526961920a229e0bb5fb459952be89fce2255 Mon Sep 17 00:00:00 2001 From: Alexander Kanavin Date: Wed, 23 Jan 2019 17:17:35 +0100 Subject: [PATCH] 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 Signed-off-by: Richard Purdie --- meta/classes/sstate.bbclass | 1 + 1 file changed, 1 insertion(+) 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" -- 2.40.1