From: "Daniel P. Berrange" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] RFC: changing ROM bundling in tar dists for releases
Date: Fri, 1 Sep 2017 10:24:07 +0100 [thread overview]
Message-ID: <20170901092407.GE31680@redhat.com> (raw)
In-Reply-To: <1504254677.10150.3.camel@redhat.com>
On Fri, Sep 01, 2017 at 10:31:17AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > > - The qemu release dists get ever larger as we add more ROMS.
> > > Adding
> > > EFI ROM builds for i386, x86_64, and aarch64 will make the dists
> > > larger still.
> >
> > I think these make sense. Should we tie this into the
> > recent suggestion (by Gerd?) that we should put all the
> > rom blobs into git submodules, and otherwise generally
> > try to regularise our handling of blobs?
>
> It surely makes sense to consider both together, so we can work out a
> reasonable workflow for firmware updates and distribution.
>
> I think it makes sense to create a separate project for the firmware
> blobs. Move over the firmware binaries and source submodules to the
> new project. This way updating both firmware sources and binaries can
> be done with a single commit, like we handle this today, just in the
> new firmware repo instead of the main qemu repo.
>
> When moving only the binaries to a separate git submodule and
> continuing to have the sources as main qemu repo submodules firmware
> updates become more complicated.
>
> > > 3. Change existing dist, and add a new one with bundled bits
> > >
> > > qemu-X.Y.Z.tar.bz2 - qemu source only
> > > qemu-addons-X.Y.Z.tar.bz2 - bundled ROMS + libs
>
> With the scheme above it makes sense to have a qemu-firmware-
> ${version}.tar.gz addon tarball. Maybe even two (one with the prebuilt
> binaries and one with the sources).
>
> Question is what to do with the non-firmware submodules (pixman, dtc,
> more?) then. I think they are not that big, so I doubt it is worth the
> hassle to create two tarball versions. And license-wise it isn't a
> issue too.
I've always wondered why we need to specialcase those modules at all.
Personally I'd just remove them entirely and let people install the
-dev packages on their distro just like they do for any other build
prerequisite of QEMU.
Regards,
Daniel
--
|: 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:[~2017-09-01 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 12:29 [Qemu-devel] RFC: changing ROM bundling in tar dists for releases Daniel P. Berrange
2017-08-31 12:49 ` Peter Maydell
2017-09-01 8:31 ` Gerd Hoffmann
2017-09-01 9:24 ` Daniel P. Berrange [this message]
2017-09-01 9:49 ` Gerd Hoffmann
2017-09-01 11:00 ` Peter Maydell
2017-09-01 14:11 ` Gerd Hoffmann
2017-09-01 15:13 ` Daniel P. Berrange
2017-09-01 17:45 ` Gerd Hoffmann
2017-08-31 15:47 ` Philippe Mathieu-Daudé
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=20170901092407.GE31680@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@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.