public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Ross Burton <Ross.Burton@arm.com>
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: Tue, 7 Oct 2025 11:36:34 +0200	[thread overview]
Message-ID: <18ea0a5d-036e-407e-96bd-ac1e6209ccc3@cherry.de> (raw)
In-Reply-To: <9179d213-ebd5-43d9-8748-6981807c29f6@oss.qualcomm.com>

On 10/6/25 10:51 PM, Dmitry Baryshkov wrote:
> 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.
> 

That's making mesa-demos kind of a meta package that pulls in everything 
built by the recipe and at the same time the only package bringing 
binaries other than the info ones.

Can you simply add this to the commit log/as a comment so that we can 
remove this RDEPENDS in the future if we want to without having to guess 
why it's there? It doesn't reflect an actual dependency but a personal 
preference.

We could also use RRECOMMENDS here to show it's even not required per-se 
but we think you probably want the info packages too.

Cheers,
Quentin


  reply	other threads:[~2025-10-07  9:36 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
2025-10-07  9:36       ` Quentin Schulz [this message]
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=18ea0a5d-036e-407e-96bd-ac1e6209ccc3@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=Ross.Burton@arm.com \
    --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