Earl Chase <[email protected]> writes:
Le dim. 18 oct. 2026 à 12:35, Morgan Smith
<[email protected]> a écrit :
Earl Chase <[email protected]> writes:
Yeah, I didn't think about that. It takes hours to build emacs
using your definitions for Emacs 28, 29, and 30?
I recently built the following list of packages in 1 go. It took
15 minutes but that was parallelized across 4 jobs. It is my
understanding that CI is generally single core so that 15m becomes
1 hour (or maybe even longer since I have 8 cores). It is also my
understanding that CI is often not very performant when compared
to dedicated hardware. You'd have to test it to be sure but I'd
say "hours" is roughly the correct range.
emacs-32-org-10.0-pre.drv
emacs-org-10.0-pre.drv
emacs-30-org-10.0-pre.drv
emacs-29-org-10.0-pre.drv
emacs-28-org-10.0-pre.drv
emacs-org-10.0-pre-0.878ae4d.drv
emacs-org-10.0-pre-0.031cf06.drv
emacs-minimal-30.2.drv
emacs-minimal-29.4.drv
emacs-minimal-28.2.drv
emacs-org-TZ=America-New_York-10.0-pre.drv
emacs-org-TZ=Europe-Istanbul-10.0-pre.drv
emacs-org-LANG=he_IL.UTF-8-10.0-pre.drv
emacs-org-LANG=de_DE.UTF-8-10.0-pre.drv
emacs-org-LANG=fr_FR.UTF-8-10.0-pre.drv
emacs-org-LANG=en_US.UTF-8-10.0-pre.drv
emacs-org-LANG=C.UTF-8-10.0-pre.drv
I didn't realize you also used Guix! If you're already
invested in Guix then please do continue that! This is my
first time encountering another user in the wild :P
I just use the package manager. I also set up a guix.scm for all
of my elisp projects so that I can test in a container. I
haven't gone as far as installing the OS yet, as I don't have
the time for that currently.
No need for the OS to simply play with the build environment and
package management features!
