[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] RFC: changing ROM bundling in tar dists for releases
From: |
Daniel P. Berrange |
Subject: |
Re: [Qemu-devel] RFC: changing ROM bundling in tar dists for releases |
Date: |
Fri, 1 Sep 2017 16:13:40 +0100 |
User-agent: |
Mutt/1.8.3 (2017-05-23) |
On Fri, Sep 01, 2017 at 04:11:44PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > 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.
>
> i.e. something like this:
>
> https://www.kraxel.org/cgit/qemu-firmware/
>
> (only seabios is there for now)
So presumably we'd want a 'make install' target there too, to place the
various ROMS in the location QEMU expects ?
So non-distro users would need to download & install the ROMs,
and then download, build & install QEMU ?
How would you view ROM install working for devs working against GIT ?
eg when we update a ROM in the firmware directory, how do devs know to
update their firmware. Would the qemu-firmware.git be a submodule of
qemu.git, so that a 'make install' would deploy roms for devs ?
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 :|