From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Michael Roth <michael.roth@amd.com>,
qemu-devel <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH v2 for-8.0 0/5] scripts/make-release: Decrease size of the release tarballs
Date: Tue, 29 Nov 2022 08:12:44 +0000 [thread overview]
Message-ID: <Y4W+/OZWjVZz75pU@redhat.com> (raw)
In-Reply-To: <CABgObfbTBN3t-OttM9gm75yPv8-5GDrp0v_Zeob0u-mp4hSQBA@mail.gmail.com>
On Mon, Nov 28, 2022 at 08:25:24PM +0100, Paolo Bonzini wrote:
> Il lun 28 nov 2022, 18:04 Daniel P. Berrangé <berrange@redhat.com> ha
> scritto:
>
> > With my distro maintainer hat I would rather QEMU ship neither the
> > ROM source, nor the ROM binaries.
> >
>
> Annd since QEMU can finally cross compile its embedded firmware modules,
> too, it is now easier for distros not to use any prebuilt binary.
>
> However some firmware sources are only available from QEMU's submodules. So
> either we distribute those submodules as separate tarballs, or distros
> would need to use the bundled tarball as well.
If the firmware doesn't exist as a standalone project, IMHO, it is
fine to bundle their sources with QEMU. If they move off into a
separate project some time in arbitrary future, they can be unbundled
at that point.
> Separately, I am not even sure what compiler is needed for the old
> Macintosh ROMs...
That we're not sure how to build some ROMS is exactly why
distros have their build everything from source policy !
With 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:[~2022-11-29 8:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 9:25 [PATCH v2 for-8.0 0/5] scripts/make-release: Decrease size of the release tarballs Thomas Huth
2022-11-28 9:25 ` [PATCH v2 for-8.0 1/5] scripts/make-release: Add a simple help text for the script Thomas Huth
2022-11-28 16:47 ` Alex Bennée
2022-11-28 9:25 ` [PATCH v2 for-8.0 2/5] scripts/make-release: Only clone single branches to speed up " Thomas Huth
2022-11-28 16:54 ` Alex Bennée
2022-11-28 9:25 ` [PATCH v2 for-8.0 3/5] scripts/make-release: Remove CI yaml and more git files from the tarball Thomas Huth
2022-11-28 16:55 ` Alex Bennée
2022-11-28 9:25 ` [PATCH v2 for-8.0 4/5] roms: Add a README file with some basic information Thomas Huth
2022-11-28 16:58 ` Alex Bennée
2022-11-28 9:25 ` [PATCH v2 for-8.0 5/5] scripts/make-release: Move roms into separate tarball Thomas Huth
2022-11-28 16:51 ` Stefan Hajnoczi
2022-11-30 11:10 ` Thomas Huth
2022-11-28 16:58 ` Alex Bennée
2022-11-28 16:53 ` [PATCH v2 for-8.0 0/5] scripts/make-release: Decrease size of the release tarballs Stefan Hajnoczi
2022-11-28 17:04 ` Daniel P. Berrangé
2022-11-28 19:25 ` Paolo Bonzini
2022-11-29 8:12 ` Daniel P. Berrangé [this message]
2022-11-29 12:56 ` Paolo Bonzini
2022-11-30 9:39 ` Mark Cave-Ayland
2022-11-30 10:49 ` Thomas Huth
2022-11-30 12:09 ` Daniel P. Berrangé
2022-12-09 8:07 ` Thomas Huth
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=Y4W+/OZWjVZz75pU@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.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 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.