From: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
To: Ross Burton <Ross.Burton@arm.com>,
"quentin.schulz@cherry.de" <quentin.schulz@cherry.de>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] mesa-demos: split info tools to a separate package
Date: Mon, 6 Oct 2025 23:51:21 +0300 [thread overview]
Message-ID: <9179d213-ebd5-43d9-8748-6981807c29f6@oss.qualcomm.com> (raw)
In-Reply-To: <282130EB-8DFE-45D1-A1C1-B7720DCB615D@arm.com>
On 06/10/2025 19:39, Ross Burton wrote:
> On 6 Oct 2025, at 15:01, Quentin Schulz via lists.openembedded.org <quentin.schulz=cherry.de@lists.openembedded.org> wrote:
>>
>> Is there really a dependency from demo applications on the various info binaries?
>>
>> Can you justify this dependency?
>>
>> Otherwise this looks good to me.
>
> I’m not Dmitry, but I’d imagine so that if you install mesa-demos you get _all_ of mesa-demos, but you can just install mesa-demos-info for just the info tools if desired.
Exactly. The distros / users might be pulling mesa-demos and expecting
both kinds of apps. Let's not disappoint them.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2025-10-06 20:51 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 ` [OE-core] " Quentin Schulz
2025-10-06 16:39 ` Ross Burton
2025-10-06 20:51 ` Dmitry Baryshkov [this message]
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=9179d213-ebd5-43d9-8748-6981807c29f6@oss.qualcomm.com \
--to=dmitry.baryshkov@oss.qualcomm.com \
--cc=Ross.Burton@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=quentin.schulz@cherry.de \
/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