public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Yu, Mingli" <mingli.yu@eng.windriver.com>,
	alexandre.belloni@bootlin.com
Cc: openembedded-core@lists.openembedded.org, Ross.Burton@arm.com
Subject: Re: [OE-core] [PATCH v3] qemu: Add qemu-common package
Date: Wed, 19 Jul 2023 11:08:48 +0100	[thread overview]
Message-ID: <a49258e57c93b7aafd3269952e073f24d5c217a6.camel@linuxfoundation.org> (raw)
In-Reply-To: <078073d8-60c9-1cdd-e7be-cd3cf63e7dda@windriver.com>

On Wed, 2023-07-19 at 17:39 +0800, Yu, Mingli wrote:
> On 7/19/23 17:24, Richard Purdie wrote:
> > > 
> > > It is relevant, this is because of the dependency that this gets built
> > > and fails. I've seen v4 but didn't have the time to test it yet.
> > 
> > I've still not seen an answer to Ross' question or mine about why we
> > can't just add a couple of dependencies and resolve things that way.
> 
> Sorry for delayed respond!
> 
> Have added qemu-common to make qemu as meta package to keep backward 
> compatibility. For user who install qemu rpm such as 
> qemu-7.2.0-r0.corei7_64.rpm, it still pull in all of things as before. 
> For user who cares the rpm size, can just choose to install the needed 
> qemu arch rpms such as qemu-system-aarch64-7.2.0-r0.corei7_64.rpm.

So why not just add:

RRECOMMENDS:${PN} += "${PN}-system-all ${PN}-user-all"

as I think we've then covered all the options we need?

Cheers,

Richard


  reply	other threads:[~2023-07-19 10:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15  8:17 [PATCH] qemu: Install the default qemu emulation rpm mingli.yu
2023-06-26 10:28 ` [OE-core] " Richard Purdie
2023-06-27 10:56   ` [PATCH] qemu: Add qemu-common package mingli.yu
2023-07-06 11:36     ` [OE-core] " Ross Burton
2023-07-10  6:55       ` [PATCH v2] " mingli.yu
2023-07-10 10:32       ` [PATCH v3] " mingli.yu
2023-07-10 20:47         ` [OE-core] " Alexandre Belloni
2023-07-12  2:39           ` Yu, Mingli
2023-07-16 11:47         ` Alexandre Belloni
2023-07-17  7:10           ` Yu, Mingli
2023-07-17 12:46             ` Alexandre Belloni
2023-07-19  9:10               ` Yu, Mingli
2023-07-19  9:20                 ` Alexandre Belloni
2023-07-19  9:24                   ` Richard Purdie
2023-07-19  9:39                     ` Yu, Mingli
2023-07-19 10:08                       ` Richard Purdie [this message]
2023-07-20  2:39                         ` Yu, Mingli

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=a49258e57c93b7aafd3269952e073f24d5c217a6.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Ross.Burton@arm.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=mingli.yu@eng.windriver.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