summaryrefslogtreecommitdiff
path: root/meta/recipes-extended/psmisc
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2015-01-26 14:40:40 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-02-03 14:53:40 +0000
commitb198a189228648057c3be7d068598f50841b3bf9 (patch)
tree706c01c34e70b9f98a41870a729977dd6b5abd6c /meta/recipes-extended/psmisc
parentcbe9d2f748125aa2dffc829570d46f8dbc1781a4 (diff)
downloadopenembedded-core-b198a189228648057c3be7d068598f50841b3bf9.tar.gz
openembedded-core-b198a189228648057c3be7d068598f50841b3bf9.tar.bz2
openembedded-core-b198a189228648057c3be7d068598f50841b3bf9.zip
classes/image: ensure uninstalled packages do not appear in manifests
Since the rewrite of the image construction code in python a few releases ago, we remove a couple of packages from the image as one of the final steps when constructing the image (notably update-rc.d and run-postinsts). However, because of the order of operations, these packages are still listed both in the buildhistory installed_package*.txt files and in the manifest file created next to the image, which is wrong. There were two possible solutions to this: (1) change the order such that the uninstallation occurs before calling ROOTFS_POSTPROCESS_COMMAND or (2) add another hook variable in such that we can have the package list collection code run at the right time. Because it's currently possible (but very much not recommended) to install additional packages within ROOTFS_POSTPROCESS_COMMAND, which may have postinstall scripts and thus require the packages we would otherwise uninstall if we were to take option 1, option 2 is really the least likely to cause problems. Therefore, add ROOTFS_POSTUNINSTALL_COMMAND and make the image and buildhistory classes use it. Fixes [YOCTO #6479]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Diffstat (limited to 'meta/recipes-extended/psmisc')
0 files changed, 0 insertions, 0 deletions