qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RfC PATCH 0/3] edk2: add efi firmware builds
Date: Mon, 28 Nov 2016 11:07:34 +0100	[thread overview]
Message-ID: <1480327654.20061.43.camel@redhat.com> (raw)
In-Reply-To: <20161123145433.GH6750@redhat.com>

  Hi,

> 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".

Or they don't even use the bundled rom sources and build from upstream
tarball instead.

> 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.

Makes sense.

> 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

Adding some submodule (roms/prebuilt?) would also make the management
easier.

Basically the full tarball would be qemu plus submodules, and the
minimal tarball would be qemu without submodules.  You can simply use
"git archive" to create the later, which is a bit problematic today as
the tarball will include blobs without sources.

cheers,
  Gerd

      reply	other threads:[~2016-11-28 10:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23 13:24 [Qemu-devel] [RfC PATCH 0/3] edk2: add efi firmware builds Gerd Hoffmann
2016-11-23 13:24 ` [Qemu-devel] [RfC PATCH 1/3] edk2: add submodule Gerd Hoffmann
2016-11-23 13:24 ` [Qemu-devel] [RfC PATCH 2/3] edk2: add build script and rules Gerd Hoffmann
2016-11-23 13:24 ` [Qemu-devel] [RfC PATCH 3/3] edk2: use EfiRom utility from edk2 submodule Gerd Hoffmann
2016-11-23 14:54 ` [Qemu-devel] [RfC PATCH 0/3] edk2: add efi firmware builds Daniel P. Berrange
2016-11-28 10:07   ` Gerd Hoffmann [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=1480327654.20061.43.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=berrange@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).