Richard Purdie 000b7d3d1c bitbake: data_smart: Ensure _remove operations on newly set variables are cleared ... We clear append/prepend on newly set variables, we should also clear remove operations. If we don't do this, there is no way we can actually delete a remove operation. Bitbake internally uses parsing=True to avoid these side effects when making its own internal calls. Also add a testcase to bitbake-selftest to ensure we remain consistent going forward from here. (Bitbake rev: 3a319f079d699c870d8531e051ab65e6278d1fa5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2017-04-12 15:09:58 +01:00
..
__init__.py	bitbake: Fixup bitbake-selftest	2012-05-04 17:41:47 +01:00
codeparser.py	bitbake: bitbake-selftest: add contains tests	2017-04-05 23:19:17 +01:00
cow.py	bitbake: tests: assertEquals -> assertEqual	2016-05-11 10:34:30 +01:00
data.py	bitbake: data_smart: Ensure _remove operations on newly set variables are cleared	2017-04-12 15:09:58 +01:00
fetch.py	bitbake: fetch2: handle absolute paths in subdir	2016-09-22 11:18:11 +01:00
parse.py	bitbake: bitbake: remove True option to getVarFlag calls	2016-11-30 15:48:09 +00:00
utils.py	bitbake: tests/utils.py: test origvalue in a callback matches what is expected	2016-04-09 23:00:46 +01:00