From: "Daniel P. Berrange" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC] dist: create separate dist with bundled roms/libs
Date: Tue, 2 May 2017 15:02:52 +0100 [thread overview]
Message-ID: <20170502140252.GA16624@redhat.com> (raw)
In-Reply-To: <20170502132456.GD22502@stefanha-x1.localdomain>
On Tue, May 02, 2017 at 02:24:56PM +0100, Stefan Hajnoczi wrote:
> On Thu, Apr 20, 2017 at 01:16:39PM +0100, Daniel P. Berrange wrote:
> > The qemu-XXXX.tar.bz2 currently contains bundled copies of the pixman
> > and dtc codebases, as well as pre-built ROM binaries and their sources.
> >
> > Many OS distros want to build & ship ROMs separately to ensure license
> > compliance. Similarly they'll build pixman/dtc code independantly to
> > allow sharing with the rest of the distro. Thus they'll never use these
> > bundled files. A further complication is that these bundled files create
> > extra auditing work for distros when applying for export compliance,
> > particularly when the bundled files contain crypto code. This burden
> > applies merely by having the files in the tar.bz2, even if they're not
> > built into the binaries. If we ever want to include UEFI ROMs for x86
> > or AArch64, then the size of the QEMU dist will increase significantly
> > more.
> >
> > The bundled ROMs though are fairly useful to end-users who are building
> > QEMU themselves and don't want to worry about figuring out the right
> > BIOS bits to build manually, so they shouldn't be dropped entirely.
> >
> > This change thus alters 'make dist' to generate two release archives
> >
> > - qemu-XXX.tar.bz2 - minimal archive with only QEMU source code
> > - qemu-bundled-XXX.tar.bz2 - QEMU source, plus bundled ROMs & libs
> >
> > NB1, as it stands this change breaks "make install" since that assumes
> > existance of the pre-built ROMs in tree.
>
> It would be good to fix this so that a minimal dist can build and
> install successfully.
Of course, I simply didn't want to sink time into it until we had a
little discussion about whether this is even the right direction
to take.
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 :|
prev parent reply other threads:[~2017-05-02 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 12:16 [Qemu-devel] [PATCH RFC] dist: create separate dist with bundled roms/libs Daniel P. Berrange
2017-04-20 12:57 ` no-reply
2017-05-02 13:24 ` Stefan Hajnoczi
2017-05-02 14:02 ` Daniel P. Berrange [this message]
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=20170502140252.GA16624@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).