From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Andreas Enge <andreas@enge.fr>
Cc: 73242@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#73242] [PATCH] gnu: guile-static-initrd: Remove (sxml) module hierarchy.
Date: Mon, 16 Sep 2024 12:11:28 +0000 [thread overview]
Message-ID: <15BC73F8-3264-44CF-B189-FA49A8AE62AE@tobias.gr> (raw)
In-Reply-To: <ZugcLHRlPrzOfw0K@jurong>
Hi Andreas,
On 16 September 2024 11:53:16 UTC, Andreas Enge <andreas@enge.fr> wrote:
>Am Sat, Sep 14, 2024 at 04:56:50AM +0200 schrieb Tobias Geerinckx-Rice:
>> If anything is ‘useless in an initrd’ it better be XML support. As of
>> Guile 3.0.9, removing it saves 1418K bytes uncompressed, or 3% of the
>> total static Guile size.
>
>I do not know why I am in cc, having no particular knowledge of initrds;
Because you foolishly volunteered for the 'core packages' team covering (gnu packages make-bootstrap). :-)
Since you bring it up: no, %guile-static-initrd doesn't particularly belong there. It's there only to keep MAKE-GUILE-STATIC-STRIPPED private.
In fact I'd move it to (gnu system linux-initrd) if I choose to rewrite it to opt into modules rather than out of them. That saves more than a few megabytes more, and boots fine, at the expense of not having them available at the 'early boot REPL'.
I'll see.
>but indeed I find your argument convincing, assuming you have tested to
>boot into the resulting system.
The patch was sent from one. Thanks!
Kind regards,
T G-R
Sent on the go. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2024-09-16 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 2:56 [bug#73242] [PATCH] gnu: guile-static-initrd: Remove (sxml) module hierarchy Tobias Geerinckx-Rice via Guix-patches via
2024-09-16 11:53 ` Andreas Enge
2024-09-16 12:11 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2024-09-16 20:22 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15BC73F8-3264-44CF-B189-FA49A8AE62AE@tobias.gr \
--to=guix-patches@gnu.org \
--cc=73242@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).