I'm surprised by this behavior, which I didn't expect... I'm running "bitbake core-image-cmdline-full; bitbake generate-index" from Poky master. with PACKAGE_CLASSES = "package_ipk package_rpm package_deb"... find tmp/deploy/deb -name *.deb | wc; find tmp/deploy/rpm -name *.rpm | wc; find tmp/deploy/ipk -name *.ipk | wc 1918 1918 129927 1918 1918 135794 5404 5404 393252 with PACKAGE_CLASSES = "package_rpm package_deb package_ipk"... find tmp/deploy/deb -name *.deb | wc; find tmp/deploy/rpm -name *.rpm | wc; find tmp/deploy/ipk -name *.ipk | wc 1918 1918 129927 5404 5404 393606 1918 1918 135584 with PACKAGE_CLASSES = "package_deb package_ipk package_rpm"... find tmp/deploy/deb -name *.deb | wc; find tmp/deploy/rpm -name *.rpm | wc; find tmp/deploy/ipk -name *.ipk | wc 5404 5404 376187 1918 1918 135794 1918 1918 135584 So, more packages are generated to the first item in PACKAGE_CLASSES. It's expected to have the first item in PACKAGE_CLASSES that is used to generate the image, but I expected all packages to be generated for all package types anyway. Isn't this the expected behavior? Otherwise, how would you generate 3 types of feeds (rpm, deb and ipk) at the same time?
According to Richard Purdie (thanks!), this is actually expected behavior. Using "bitbake --runall build <image>" allows to get the same number of packages. See https://lore.kernel.org/openembedded-core/c0b1cf77-830b-4838-a92c-cd0d70c1bb05@bootlin.com/T/#t Closing this bug.