Richard Purdie 353212a533 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 rev: ed74ea50043f6feb698c891e571feda2b9f8513d)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

2013-06-21 09:19:28 +01:00

..

bb

bitbake: data_smart: Ensure variable flags are accounted for in config data hash

2013-06-21 09:19:28 +01:00

ply

Add pysh, ply, and codegen to lib/ to prepare for future work

2010-08-03 14:06:07 +01:00

prserv

bitbake: prserv: Adapt autostart to bitbake-worker

2013-06-14 12:52:57 +01:00

codegen.py

Add pysh, ply, and codegen to lib/ to prepare for future work

2010-08-03 14:06:07 +01:00

progressbar.py

Experimental usage of the 'progressbar' module

2011-01-04 14:46:42 +00:00