From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Michael Tokarev" <mjt@tls.msk.ru>,
"Michael Roth" <michael.roth@amd.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH] scripts/make-release: Go back to cloning all the EDK2 submodules
Date: Mon, 21 Jul 2025 16:41:50 +0100 [thread overview]
Message-ID: <CAFEAcA8LjHXrkiAg-pmRrfBgMohUQU805mX5W0JznVm=qMuWMg@mail.gmail.com> (raw)
In-Reply-To: <20250721153341.2910800-1-peter.maydell@linaro.org>
On Mon, 21 Jul 2025 at 16:33, Peter Maydell <peter.maydell@linaro.org> wrote:
> I think ideally we would not ship these rom blobs in our source
> tarball but instead provide them separately. Then we would definitely
> have no reason to ship a huge amount of EDK2 sourcecode that
> 99.9% of the users of the tarball don't want. But that's an
> idea that was floated at least three or four years ago now
> and we don't in practice have time or effort to try to do that.
> So the simple thing is to at least ship the right source...
To quantify "huge amount": a 10.0.0 tarball uncompresses to
911MB; of that, 445MB is roms/edk2. Another 156MB is roms/u-boot,
and 48MB is roms/u-boot-sam460ex. roms/ overall is 743MB.
So 80% of our source tarball release is ROM blob source, and
48% of our tarball is EDK2...
-- PMM
next prev parent reply other threads:[~2025-07-21 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 15:33 [PATCH] scripts/make-release: Go back to cloning all the EDK2 submodules Peter Maydell
2025-07-21 15:41 ` Peter Maydell [this message]
2025-07-21 15:50 ` Michael Tokarev
2025-07-31 17:40 ` Peter Maydell
2025-08-02 7:02 ` Michael Tokarev
2025-08-04 14:59 ` Alex Bennée
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='CAFEAcA8LjHXrkiAg-pmRrfBgMohUQU805mX5W0JznVm=qMuWMg@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=berrange@redhat.com \
--cc=michael.roth@amd.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--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).