From: kiasoc5 <kiasoc5@disroot.org>
To: Vagrant Cascadian <vagrant@debian.org>, guix-devel@gnu.org
Subject: Re: %base-packages and default grub theme depend on rust
Date: Mon, 15 Jan 2024 12:39:08 -0500 [thread overview]
Message-ID: <1ff0705e-57a9-4571-a11c-db45a70adc5d@disroot.org> (raw)
In-Reply-To: <87le8rcm92.fsf@wireframe>
Hi Vagrant,
On 1/14/24 22:24, Vagrant Cascadian wrote:
> So, I stumbled a bit with a fairly recently installed aarch64/arm64
> system. The install went fine late December, but then I tried "guix
> system reconfigure" a couple days ago, and even though it is a very
> simple configuration (based on bare-bones.tmpl with grub-efi)... it
> pretty much needed to rebuild about 12 rust versions, as no substitutes
> were available on aarch64-linux. *sigh*
>
> I thought I tracked this down to guix-icons depending on librsvg, which
> depends on rust... and guix-icons is in %base-packages.
>
> So I dropped use of %base-packages-artwork, which pulls in guix-icons
> and used all the various other %base-packages-* stuff explicitly... but
> it still wanted to pull in guix-icons/librsvg/rust-* etc ... it just did
> so later in the build process... foiled again!
>
> This is because the default grub theme generates a .png from an .svg
> ... using guile-rsvg, which uses librsvg, which uses rust ...
>
> But this machine just has a serial console, and has no need of a
> background image in the grub configuration...
>
> So eventually I figured out how to get a grub theme without a background
> image and drop guix-icons from the configuration by avoiding use of
> %base-packages-artwork:
>
> (bootloader (bootloader-configuration
> + (theme (grub-theme (image #f)))
> (bootloader grub-efi-bootloader)
> (targets '("/boot/efi"))))
>
> - (packages (cons screen %base-packages))
> + (packages (append (list screen nss-certs)
> + %base-packages-interactive
> + %base-packages-linux
> + %base-packages-networking
> + %base-packages-utils))
>
> Maybe these is a more elegant way of doing this.
>
>
> So, the example bare-bones system configuration does seems to have heavy
> layers of rust obscuring the bones.
>
> Do we want a really-quite-bare-bones configuration example?
> Should guix-icons not actually be in %base-packages?
> Can the grub theme be implemented differently without requiring rust?
At least a PNG copy of the SVG could be created ahead of time without
having to use librsvg to convert it.
> This seems like possibly a discussion so far, but I would also be happy
> to turn this into a bug report if desired!
>
>
> Thanks everyone!
>
>
> live well,
> vagrant
next prev parent reply other threads:[~2024-01-15 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 3:24 %base-packages and default grub theme depend on rust Vagrant Cascadian
2024-01-15 17:39 ` kiasoc5 [this message]
2024-01-29 16:36 ` Ludovic Courtès
2024-02-08 12:33 ` Efraim Flashner
2024-02-08 14:54 ` Janneke Nieuwenhuizen
2024-02-29 7:28 ` Efraim Flashner
2024-02-29 8:11 ` Janneke Nieuwenhuizen
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=1ff0705e-57a9-4571-a11c-db45a70adc5d@disroot.org \
--to=kiasoc5@disroot.org \
--cc=guix-devel@gnu.org \
--cc=vagrant@debian.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.
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).