Re: [Qemu-devel] [RfC PATCH 0/3] edk2: add efi firmware builds

[Daniel P. Berrange]

On Wed, Nov 23, 2016 at 02:24:41PM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> This patch series adds a edk2 submodule in roms, also a build script
> and makefile rules to build ovmf and arm firmware.
> 
> The build script creates per-arch subdirs in pc-bios and places the
> firmware files there.  They are not exactly small:
> 
>    address@hidden ~/projects/qemu (work/edk2)# du -s -h pc-bios/edk2-*
>    2,8M    pc-bios/edk2-aarch64
>    2,8M    pc-bios/edk2-arm
>    2,1M    pc-bios/edk2-i386
>    2,1M    pc-bios/edk2-x86_64
> 
> So, the question is how we wanna go forward with this.  Adding the
> submodule and rules is a no-brainer I think.  But what about the
> binaries, which sum up to roughly 10M?  Ship them all?  Ship the
> 64bit archs only, given that efi never really took off on i386
> and arm?
> 
> Other comments?

Should we think about our policy for distributing & shipping ROMS
more generally ?  Most distros will actively strip out the ROMs that
we ship in the QEMU tar.gz releases, and rebuild them from pristine
source in order to ensure they're fully complying with licensing
requirements wrt "full & corresponding source".

So should we consider actually shipping 2 tar.gz files for QEMU
releases. One minimal qemu-x.y.z.tar.gz that only contains pristine
QEMU source with no pre-built artifacts, and a second qemu-full-x.y.z.tar.gz
that contains the QEMU source, plus an arbitrary number of pre-built
blobs.

Alternatively, instead of a qemu-full-x.y.z.tar.gz, we could just
have a qemu-roms-x.y.z.tar.gz bundle which only contained the ROMs,
which users would use in combination with the other releae.

Vendors would use the minimal release, while users who just want to
build their own QEMU with least effort would  use the full release
tar.gz

If we had some split like this, then I think we would not have to
really worry about the fact that the ROMs will get quite large
as the size would only impact people wanting to download the full
release.

In terms of GIT, we could likewise make the binary ROMS live in
a submodule, so we don't bloat the main GIT repo, but I don't
think that's so critical

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://entangle-photo.org       -o-    http://search.cpan.org/~danberr/ :|