public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: rpjday@crashcourse.ca,
	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: Mon, 02 Sep 2024 11:56:08 +0100	[thread overview]
Message-ID: <dbba02a3a7967229e2133e69cd636349ac5374a4.camel@linuxfoundation.org> (raw)
In-Reply-To: <5557141e-86f6-1a86-2069-9f566e766385@crashcourse.ca>

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


  reply	other threads:[~2024-09-02 10:56 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 ` Richard Purdie [this message]
2024-09-02 11:04   ` [OE-core] " Robert P. J. Day
2024-09-03  3:26     ` ChenQi

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=dbba02a3a7967229e2133e69cd636349ac5374a4.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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