From: Peter Xu <peterx@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Devel Mailing List <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Is there a way to package QEMU binaries?
Date: Wed, 13 Jun 2018 12:02:59 +0800 [thread overview]
Message-ID: <20180613040259.GI15344@xz-mi> (raw)
In-Reply-To: <CAFEAcA_Bh4U1X_FDbakcc7YDBHFrkCjCKGrtuTWegn7rAGZUeQ@mail.gmail.com>
On Tue, Jun 12, 2018 at 09:52:45AM +0100, Peter Maydell wrote:
> On 12 June 2018 at 07:24, Peter Xu <peterx@redhat.com> wrote:
> > For example, I wanted to compile QEMU once and install it on multiple
> > systems. What would be the suggested way to do so?
>
> For this, I would recommend using whatever the packaging
> format for those systems is. Eg for Debian use the existing
> Debian QEMU packages, for Redhat systems use RPMs, etc.
> If you want a newer version of QEMU than is in the distro's
> packages, you can probably forward port the packaging parts
> to a newer QEMU without too much pain.
>
> Or you can use a distro-agnostic packaging tool of some sort;
> there are a few out there but I have no particular recommendations.
I'll start my investigation with RPM first. Thanks Peter.
--
Peter Xu
next prev parent reply other threads:[~2018-06-13 4:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 6:24 [Qemu-devel] Is there a way to package QEMU binaries? Peter Xu
2018-06-12 6:41 ` Fam Zheng
2018-06-12 6:52 ` Peter Xu
2018-06-12 7:01 ` Fam Zheng
2018-06-12 7:41 ` Peter Xu
2018-06-12 7:53 ` Liviu Ionescu
2018-06-13 3:48 ` Peter Xu
2018-06-12 11:34 ` Laszlo Ersek
2018-06-12 11:29 ` Laszlo Ersek
2018-06-13 3:46 ` Peter Xu
2018-06-12 8:52 ` Peter Maydell
2018-06-13 4:02 ` Peter Xu [this message]
2018-06-13 9:28 ` Daniel P. Berrangé
2018-06-14 2:55 ` Peter Xu
2018-06-14 8:14 ` Daniel P. Berrangé
2018-06-14 10:50 ` Peter Maydell
2018-06-14 11:03 ` Peter Xu
2018-06-14 12:58 ` Alex Bennée
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=20180613040259.GI15344@xz-mi \
--to=peterx@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.