diff options
author | Ross Burton <ross.burton@intel.com> | 2018-03-02 14:06:49 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-03-06 06:19:18 -0800 |
commit | be18eff13960421a56dee23d4eac91320d3e3e66 (patch) | |
tree | cefd98d4be3d574ad1c675f990a412b7327c4b42 /meta/recipes-rt | |
parent | bd5424f5b05a0a65471a77632efe7b9907370217 (diff) | |
download | poky-be18eff13960421a56dee23d4eac91320d3e3e66.tar.gz |
xcb-proto: solve python cache collision
Because I didn't really want python3-native to be at the bottom of the
entire X11 stack this recipe jumps through a small hoop to use the host
Python to run some modules it installs into the sysroot.
The Makefile compiles the Python module, which is good as the cache file
is recorded in the sstate manifest so when the package is removed from the
sysroot all of it is removed.
However in an enviroment where the sstate is shared between multiple hosts
it is possible that a different Python is used and this will generate a
new cache when the code is executed, which is not recorded in the manifest.
Eventually you'll end up with ownerless cache files in a sysroot which
conflict with the same file coming from a sstate upgrade.
Solve this with a SSTATE_INST_POSTRM which is ran when sstate is removed
to ensure that there are no Python cache files left behind.
[ YOCTO #11809 ]
(From OE-Core rev: 6f6a2b5ff7ec23bd3782f0c3521f3576101cbc9d)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-rt')
0 files changed, 0 insertions, 0 deletions