From: André Draszik <[email protected]> When uninstalling update-alternatives, it doesn't seem to make much sense to keep the update-alternatives database around. In particular when removing packaging data, e.g. due to read-only rootfs, update-alternatives is removed from the target file system. Leaving its database around serves no purpose in that case as there is no way to use it afterwards anyway.
This frees close to 700KB of (uncompressed) space in a busybox based environment. Signed-off-by: André Draszik <[email protected]> --- meta/recipes-devtools/opkg-utils/opkg-utils_git.bb | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb b/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb index a7aec45..19a852e 100644 --- a/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb +++ b/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb @@ -43,4 +43,9 @@ RPROVIDES_update-alternatives-opkg = "update-alternatives update-alternatives-cw RREPLACES_update-alternatives-opkg = "update-alternatives-cworth" RCONFLICTS_update-alternatives-opkg = "update-alternatives-cworth" +pkg_postrm_update-alternatives-opkg() { + rm -rf $OPKG_OFFLINE_ROOT${nonarch_libdir}/opkg/alternatives + rmdir --ignore-fail-on-non-empty $OPKG_OFFLINE_ROOT${nonarch_libdir}/opkg +} + BBCLASSEXTEND = "native nativesdk" -- 2.10.2 -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
