From: ChenQi <Qi.Chen@windriver.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] why does EXTRA_IMAGE_FEATURES += "ptest-pkgs" not install *all* ptest pkgs?
Date: Tue, 3 Sep 2024 11:26:56 +0800 [thread overview]
Message-ID: <9f62dec2-203f-4d47-a435-d0dbf5c93622@windriver.com> (raw)
In-Reply-To: <6e65acdb-454-65ec-8dda-ad9f746468d@crashcourse.ca>
On 9/2/24 19:04, Robert P. J. Day wrote:
> On Mon, 2 Sep 2024, Richard Purdie wrote:
>
>> On Mon, 2024-09-02 at 06:39 -0400, Robert P. J. Day via lists.openembedded.org wrote:
>>> i'm sure i've overlooked something silly, but in building a
>>> qemuarm64 image to demo ptest to some colleagues, poky by default sets
>>> the "ptest" DISTRO_FEATURES setting so all of the corresponding ptest
>>> packages are *built*, but when adding:
>>>
>>> EXTRA_IMAGE_FEATURES += "ptest-pkgs"
>>>
>>> only *some* of the ptest packages are added to the image. eg: while
>>> bzip2-ptest is built, it is not added to the image, as are a number of
>>> other ptest packages. if i *explicitly* add that package, then it gets
>>> included.
>>>
>>> is there some obvious reason that a number of ptest packages are not
>>> included in the resulting image, despite them being built?
>> In your example, was bzip2 actually in your image or was it only built?
>>
>> I suspect it only installs ptests for things actually in the image.
> yup, i read in the ptest wiki page that the ptests are installed
> only when the associated regular package is also installed, and i did
> verify that bzip2 was installed.
>
> oh, wait ... damn it ... just noticed that my build incorporates
> busybox, which probably gets in the way of installing *numerous*
> ptest packages that would normally be installed. does that sound like
> the culprit?
>
> rday
As far as I know, if bzip2 is brought in by some other package's ptest
(e.g., A-ptest rdepends on bzip2), then bzip2-ptest will not be
installed. It's not just ptest, all complementary packages have this
problem.
Regards,
Qi
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#204093): https://lists.openembedded.org/g/openembedded-core/message/204093
> Mute This Topic: https://lists.openembedded.org/mt/108224395/7304865
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [Qi.Chen@eng.windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
prev parent reply other threads:[~2024-09-03 3:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 10:39 why does EXTRA_IMAGE_FEATURES += "ptest-pkgs" not install *all* ptest pkgs? Robert P. J. Day
2024-09-02 10:56 ` [OE-core] " Richard Purdie
2024-09-02 11:04 ` Robert P. J. Day
2024-09-03 3:26 ` ChenQi [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=9f62dec2-203f-4d47-a435-d0dbf5c93622@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=rpjday@crashcourse.ca \
/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