aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/python/python3/python3-manifest.json
diff options
context:
space:
mode:
authorRoss Burton <ross.burton@intel.com>2018-01-26 10:44:35 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-01-29 08:49:44 +0000
commita321b28c8dafc9775f465ce7c0f6bcbe8ccc2945 (patch)
tree80c927c15a5d8dffbeda8d837e9c4e34a1b20500 /meta/recipes-devtools/python/python3/python3-manifest.json
parent8644d7bde6a30aec4e666ad59ff148f04c616a21 (diff)
downloadopenembedded-core-contrib-a321b28c8dafc9775f465ce7c0f6bcbe8ccc2945.tar.gz
python: fix parse dependencies
Adding a file-checksums flag for the manifest to do_split_packages doesn't achieve anything as do_split_packages isn't a task. Changing this to tha task do_package shows that the path is wrong, but we also know that as the manifest is in SRC_URI any changes to it would result in a rebuild anyway, so this line can be deleted. However there is a problem of the recipe not being reparsed when it needs to be, if the JSON has changed. The main bitbake process can hash the recipe and use stale data from the cache as it hasn't considered the manifest file changing. This results in non-determinism warnings when the worker parses the recipe again and comes to a different hash (as the manifest has changed, so the packaging changed). Solve this by calling bb.parse.mark_dependency() to declare the dependency on the manifest. Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/recipes-devtools/python/python3/python3-manifest.json')
0 files changed, 0 insertions, 0 deletions