From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: Shouldn't packages for all PACKAGE_CLASSES be generated?
Date: Thu, 1 Feb 2024 13:47:45 +0100 [thread overview]
Message-ID: <c0b1cf77-830b-4838-a92c-cd0d70c1bb05@bootlin.com> (raw)
Greetings,
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?
Cheers
Michaell
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2024-02-01 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 12:47 Michael Opdenacker [this message]
2024-02-02 15:57 ` [OE-core] Shouldn't packages for all PACKAGE_CLASSES be generated? Richard Purdie
2024-02-02 19:02 ` Michael Opdenacker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c0b1cf77-830b-4838-a92c-cd0d70c1bb05@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox