From: Quentin Schulz <quentin.schulz@cherry.de>
To: dmitry.baryshkov@oss.qualcomm.com,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] mesa-demos: split info tools to a separate package
Date: Mon, 6 Oct 2025 16:01:13 +0200 [thread overview]
Message-ID: <feae4e64-0969-4e02-84b4-3ecba5e41a02@cherry.de> (raw)
In-Reply-To: <20251002015030.2464972-1-dmitry.baryshkov@oss.qualcomm.com>
Hi Dmitry,
On 10/2/25 3:50 AM, Dmitry Baryshkov via lists.openembedded.org wrote:
> While the rest of programs inside mesa-demos are really "demos", several
> *info utilities have separate value as they allow gathering information
> about the running system in a manner similar to clinfo or vulkaninfo.
> Split them into a separate package in order to allow picking them info
> the images without picking up the rest of "demos".
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---
> meta/recipes-graphics/mesa/mesa-demos_9.0.0.bb | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/meta/recipes-graphics/mesa/mesa-demos_9.0.0.bb b/meta/recipes-graphics/mesa/mesa-demos_9.0.0.bb
> index a9e84039d2c9..0bc8519e90e2 100644
> --- a/meta/recipes-graphics/mesa/mesa-demos_9.0.0.bb
> +++ b/meta/recipes-graphics/mesa/mesa-demos_9.0.0.bb
> @@ -20,6 +20,10 @@ REQUIRED_DISTRO_FEATURES = "opengl x11"
>
> EXTRA_OEMESON = "-Dwith-system-data-files=true"
>
> +PACKAGE_BEFORE_PN = "${PN}-info"
> +RDEPENDS:${PN} += " ${PN}-info"
Is there really a dependency from demo applications on the various info
binaries?
Can you justify this dependency?
Otherwise this looks good to me.
Cheers,
Quentin
next prev parent reply other threads:[~2025-10-06 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 1:50 [PATCH] mesa-demos: split info tools to a separate package Dmitry Baryshkov
2025-10-06 14:01 ` Quentin Schulz [this message]
2025-10-06 16:39 ` [OE-core] " Ross Burton
2025-10-06 20:51 ` Dmitry Baryshkov
2025-10-07 9:36 ` Quentin Schulz
2025-10-07 10:30 ` Alexander Kanavin
2025-10-07 11:02 ` Quentin Schulz
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=feae4e64-0969-4e02-84b4-3ecba5e41a02@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=dmitry.baryshkov@oss.qualcomm.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