diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-07-29 09:19:42 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-07-29 13:26:10 +0100 |
commit | 9313ff77f39abf776556cd7b0edb3c08854d68ef (patch) | |
tree | 6ffcc406ee997478f4760a266b634b8aa0609bbf | |
parent | c109e1fb18c5541aa5bf500c4622f4f7b677db08 (diff) | |
download | bitbake-9313ff77f39abf776556cd7b0edb3c08854d68ef.tar.gz |
bitbake: data_smart: Ensure variable flags are accounted for in config data hash
Currently if the flags set against a variable in the base data store
change, it doesn't automatically trigger a reparse when it really
should. For example with the blacklist class setting:
PNBLACKLIST[qemu] = "bar"
PNBLACKLIST[bash] = "foo"
will not trigger a reparse if only one entry is changed and a
blacklisted recipe can still be built.
I did consider using BB_SIGNATURE_EXCLUDE_FLAGS in here however it
doesn't make sense, we want to trigger a reparse when any of the
flags change too (which is different to the sstate signatures which
we wouldn't want to change in those cases).
[YOCTO #4627]
(Bitbake master rev: ed74ea50043f6feb698c891e571feda2b9f8513d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r-- | lib/bb/data_smart.py | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/lib/bb/data_smart.py b/lib/bb/data_smart.py index 2fd8ccdeb..fa7811e6f 100644 --- a/lib/bb/data_smart.py +++ b/lib/bb/data_smart.py @@ -738,6 +738,12 @@ class DataSmart(MutableMapping): value = d.getVar(key, False) or "" data.update({key:value}) + varflags = d.getVarFlags(key) + if not varflags: + continue + for f in varflags: + data.update({'%s[%s]' % (key, f):varflags[f]}) + for key in ["__BBTASKS", "__BBANONFUNCS", "__BBHANDLERS"]: bb_list = d.getVar(key, False) or [] bb_list.sort() |