From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Yu, Mingli" <mingli.yu@eng.windriver.com>,
openembedded-core@lists.openembedded.org
Cc: Bruce Ashfield <bruce.ashfield@gmail.com>
Subject: Re: [OE-core] [PATCH] qemu: Install the default qemu emulation rpm
Date: Mon, 26 Jun 2023 11:28:54 +0100 [thread overview]
Message-ID: <00b7c129a959d0a53f218513106c46241976d466.camel@linuxfoundation.org> (raw)
In-Reply-To: <20230615081705.96399-1-mingli.yu@eng.windriver.com>
On Thu, 2023-06-15 at 16:17 +0800, Yu, Mingli wrote:
> From: Mingli Yu <mingli.yu@windriver.com>
>
> The qemu rpm can be split or not via customize PACKAGESPLITFUNCS and
> there is no specific qemu emulation rpm installed when we choose split
> the qemu rpms now.
>
> To gurantee the basic usage, install the qemu emulation rpm which
> corresponding to the target arch by default when split the qemu rpm.
>
> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
> ---
> meta/recipes-devtools/qemu/qemu.inc | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/recipes-devtools/qemu/qemu.inc b/meta/recipes-devtools/qemu/qemu.inc
> index 7d39f0a25d..c9df43a5a2 100644
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -248,6 +248,9 @@ python split_qemu_packages () {
> mipspackage = d.getVar('PN') + "-user-mips"
> if mipspackage in ' '.join(userpackages):
> d.appendVar('RDEPENDS:' + mipspackage, ' ' + d.getVar("MLPREFIX") + 'bash')
> +
> + targetarch = "${@'i386' if d.getVar('TARGET_ARCH') in ['x86', 'i486', 'i586', 'i686'] else d.getVar('TARGET_ARCH').replace('_', '-')}"
> + d.appendVar('RRECOMMENDS:' + d.getVar('PN'), ' ' + d.getVar('PN') + '-user-' + targetarch + ' ' + d.getVar('PN') + '-system-' + targetarch)
> }
>
> # Put the guest agent in a separate package
I did originally say that I thought the qemu package should pull in all
of the sub packages to maintain compatibility. I'm not sure having it
pick the host architecture like this is a great idea and certainly it
changes the default behaviour again.
I'd much rather than picked a design then implementing it than keeping
changing behaviour like this :(.
I'm not seeing many other opinions though.
Cheers,
Richard
next prev parent reply other threads:[~2023-06-26 10:29 UTC|newest]
Thread overview: 20+ 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 ` Richard Purdie [this message]
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
2023-07-20 2:39 ` Yu, Mingli
[not found] <1768C72652DD9852.10197@lists.openembedded.org>
2023-06-26 6:00 ` [OE-core] [PATCH] qemu: Install the default qemu emulation rpm Yu, Mingli
2023-06-29 2:01 ` Yu, Mingli
2023-06-29 10:20 ` Richard Purdie
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=00b7c129a959d0a53f218513106c46241976d466.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@gmail.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