public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Shouldn't packages for all PACKAGE_CLASSES be generated?
Date: Fri, 2 Feb 2024 20:02:40 +0100	[thread overview]
Message-ID: <96563fbd-2ffb-44bd-9dbb-c61457560491@bootlin.com> (raw)
In-Reply-To: <a2ec9e318bc5e11b0ce42797293735db0b0819e2.camel@linuxfoundation.org>

Hi Richard,

Thanks for your answer!

On 2/2/24 at 16:57, Richard Purdie wrote:
> On Thu, 2024-02-01 at 13:47 +0100, Michael Opdenacker via
> lists.openembedded.org wrote:
>> 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?
> This is expected for various reasons, try adding --runall build to the
> command.


Right, it works and I'm now getting the same number of packages for all 
variants.

By the way, another surprise, ipk packages take more space than deb 
ones, at least in the feeds:

$ du -sh tmp/deploy/*
1.4G    tmp/deploy/deb
2.2G    tmp/deploy/ipk
1.6G    tmp/deploy/rpm

What makes ipk more attractive than deb for embedded cases? I can just 
find the statement that opkg is lightweight and optimized for embedded 
applications (https://git.yoctoproject.org/opkg/tree/README.md).

Thanks again
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      reply	other threads:[~2024-02-02 19:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 12:47 Shouldn't packages for all PACKAGE_CLASSES be generated? Michael Opdenacker
2024-02-02 15:57 ` [OE-core] " Richard Purdie
2024-02-02 19:02   ` Michael Opdenacker [this message]

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=96563fbd-2ffb-44bd-9dbb-c61457560491@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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