opkg-utils: don't generate PN-dev and PN-staticdev

opkg-utils ends up in any opkg/rpm image with package management as it's the
provider for update-alternatives.  If dev-pkgs is enabled then opkg-utils-dev
will get installed, which is empty but will subsequently pull python3-dev into
the image (as opkg-utils-python depends on python3).

As this can result in all of Python appearing in otherwise small images, don't
generate these pointless packages.

Signed-off-by: Ross Burton <ross.burton@intel.com>

diff --git a/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb b/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb
index 2460a26324f70f7151f262d2c149b80970b315ef..06710b596b62b4c481234f5e498d28048a606ce7 100644 (file)
--- a/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb
+++ b/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb
@@ -39,6 +39,10 @@ do_install_append_class-target() {
        fi
 }
 
+# These are empty and will pull python3-dev into images where it wouldn't
+# have been otherwise, so don't generate them.
+PACKAGES_remove = "${PN}-dev ${PN}-staticdev"
+
 PACKAGES =+ "update-alternatives-opkg"
 FILES_update-alternatives-opkg = "${bindir}/update-alternatives"
 RPROVIDES_update-alternatives-opkg = "update-alternatives update-alternatives-cworth"