From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Devel Mailing List <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Is there a way to package QEMU binaries?
Date: Thu, 14 Jun 2018 09:14:20 +0100 [thread overview]
Message-ID: <20180614081420.GG6355@redhat.com> (raw)
In-Reply-To: <20180614025521.GR15344@xz-mi>
On Thu, Jun 14, 2018 at 10:55:21AM +0800, Peter Xu wrote:
> On Wed, Jun 13, 2018 at 10:28:09AM +0100, Daniel P. Berrangé wrote:
> > On Wed, Jun 13, 2018 at 12:02:59PM +0800, Peter Xu wrote:
> > > 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.
> >
> > If you're interested in Fedora, I maintain a Copr repository which
> > provides RPMs for every QEMU version since 1.4.0 and every libvirt
> > version since 1.2.0...
> >
> > https://copr.fedorainfracloud.org/coprs/berrange/virt-ark/
> >
> > Yeah, Fedora 28 is missing, but I'll be adding it real soon.
>
> Good to know this.
>
> Then is there an easy way to port the specfile and tools to QEMU
> repository so that we can pack that even with a git tree?
The QEMU spec I'm using for virt-ark is very much cut-down and simplified
and doesn't try to follow best practices for packaging [1]
Well if we want to have a RPM spec file for QEMU distributed with upstream
QEMU, then I think it would be better todo what libvirt does[2], and simply
have the real Fedora specfile kept in QEMU git [3].
Regards,
Daniel
[1] https://pagure.io/virt-ark/blob/master/f/qemu-ark.spec.in
[2] https://libvirt.org/git/?p=libvirt.git;a=blob;f=libvirt.spec.in;hb=HEAD
[3] https://src.fedoraproject.org/rpms/qemu/blob/master/f/qemu.spec
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-06-14 8:14 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
2018-06-13 9:28 ` Daniel P. Berrangé
2018-06-14 2:55 ` Peter Xu
2018-06-14 8:14 ` Daniel P. Berrangé [this message]
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=20180614081420.GG6355@redhat.com \
--to=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).