[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#68505: [PATCH v2] Add more detailed instructions into the HACKING fi
From: |
Ludovic Courtès |
Subject: |
bug#68505: [PATCH v2] Add more detailed instructions into the HACKING file. |
Date: |
Wed, 24 Jan 2024 11:18:27 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Hi,
Tomas Volf <~@wolfsden.cz> skribis:
> Until now, the ./meta/guile was not mentioned anywhere, and therefore it
> was not obvious how to run the locally compiled Guile without installing
> it.
>
> While modifying the file, I took the liberty to also mention a bit about
> compiling Guile using Guix.
>
> Finally, the header lines where cleaned up, ensuring all of them end at
> 70 and have a leading space.
>
> * HACKING (Hacking It Yourself): Add Guix instructions. Add a note
> about meta/guile script.
> (Sample GDB Initialization File),
> (Naming conventions): Clean up the header line.
> ---
> v2:
> Add note regarding JIT and GNU Hurd. Add note regarding -fexcess-precision.
> Add --disable-static and explain it.
Much welcome addition!
> +You can spawn a shell with all the required dependencies using GNU Guix
> +by running the following command:
> +
> + guix shell -D -f guix.scm --pure
I would suggest running:
guix shell -CP
(Currently ‘README’ suggests ‘guix shell’.)
The rationale is: it’s shorter, using a container avoids interference,
and ‘-P’ works well with ‘config.cache’ & co. (because the cached file
names then are $HOME/.guix-profile/…).
WDYT?
Thanks,
Ludo’.