why does EXTRA_IMAGE_FEATURES += "ptest-pkgs" not install *all* ptest pkgs?

why does EXTRA_IMAGE_FEATURES += "ptest-pkgs" not install *all* ptest pkgs?

[Robert P. J. Day]

  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?

rday

Re: [OE-core] why does EXTRA_IMAGE_FEATURES += "ptest-pkgs" not install *all* ptest pkgs?

[Richard Purdie]

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.

Cheers,

Richard

Re: [OE-core] why does EXTRA_IMAGE_FEATURES += "ptest-pkgs" not install *all* ptest pkgs?

[Robert P. J. Day]

[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]

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

Re: [OE-core] why does EXTRA_IMAGE_FEATURES += "ptest-pkgs" not install *all* ptest pkgs?

[ChenQi]

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]
> -=-=-=-=-=-=-=-=-=-=-=-
>