all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleander via <help-guix@gnu.org>
To: kiasoc5@disroot.org, help-guix@gnu.org
Subject: Re: Build and upgrade times for heavier packages on old hardware
Date: Sun, 25 Feb 2024 08:06:13 +0000	[thread overview]
Message-ID: <8XlwnnK-6_8w4uRIotAYKtLBhnuO9ps3XWkAUIcLNuKBsruuOfp-XMFkPK8bIl5FjtXygIU0QDY8kFC9Hw-NKdepy_FuXJypS4wpZfHJjtA=@protonmail.com> (raw)
In-Reply-To: <bbe2cfb0-6c61-49be-8a9d-00625dca97ef@disroot.org>

Hi kiasoc5,
thank you.

Are substitutes in Guix System disabled by running `# guix-daemon --no-substitutes`? How can I see whether they are enabled or not?

-------- Original Message --------
On Feb 21, 2024, 21:36, kiasoc5 wrote:

> Hi Oleander, On 2/21/24 9:00 AM, Oleander via  wrote: > Hello everyone, > I'm considering disabling substitutes on my current Guix system running on an old Thinkpad with an i5-2520M, 10GB of ram and an SSD. Build times will probably take a while if all substitutes are disabled because you (might?) have to bootstrap the compilers. > Considered that many of you might be running Guix on something similar due to the compatibility between coreboot/libreboot and old Thinkpads, how long would it take approximately to build and upgrade packages like: I don't have a Thinkpad but I'll predict the packages with the longest compile times. > linux-libre If you customize your kernel for unnecessary modules, this speed up quite a bit (on my machine I can theoretically cut the time by half). > icecat This will probably take the longest. 1. Depends on bootstrapping rust first. With 10GB of RAM I'd suggest using swap. 2. Is a "modern" browser. At least it should compile faster than chromium, once all the Rusts are built. > pandoc I'm not sure about this exactly, but it does depends on Haskell bootstrap. Hopefully it's faster than Rust. > alacritty Like icecat, requires Rust. The actual app should be relatively faster to compile. Personally to estimate compile times, I build binutils to get the Standard Build Unit and reference BLFS for relative build times: https://www.linuxfromscratch.org/blfs/

  reply	other threads:[~2024-02-25  8:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 14:00 Build and upgrade times for heavier packages on old hardware Oleander via
2024-02-21 20:36 ` kiasoc5
2024-02-25  8:06   ` Oleander via [this message]
2024-02-25 22:09     ` kiasoc5
2024-02-26  9:14     ` Andreas Enge
2024-02-24 17:19 ` Csepp

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='8XlwnnK-6_8w4uRIotAYKtLBhnuO9ps3XWkAUIcLNuKBsruuOfp-XMFkPK8bIl5FjtXygIU0QDY8kFC9Hw-NKdepy_FuXJypS4wpZfHJjtA=@protonmail.com' \
    --to=help-guix@gnu.org \
    --cc=7059548@protonmail.com \
    --cc=kiasoc5@disroot.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

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.