From: Tomas Volf <~@wolfsden.cz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 68505@debbugs.gnu.org
Subject: bug#68505: [PATCH v2] Add more detailed instructions into the HACKING file.
Date: Wed, 24 Jan 2024 17:59:07 +0100 [thread overview]
Message-ID: <ZbFB29cSlyL0c_mk@ws> (raw)
In-Reply-To: <87sf2nuj9o.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
Thank you for the review.
On 2024-01-24 11:18:27 +0100, Ludovic Courtès wrote:
> > +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?
Modified as agreed on irc. I am not convinced on the -P, but I defer to your
judgment on this.
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-24 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 12:50 bug#68505: [PATCH v2] Add more detailed instructions into the HACKING file Tomas Volf
2024-01-24 10:18 ` Ludovic Courtès
2024-01-24 16:59 ` Tomas Volf [this message]
2024-01-24 16:48 ` bug#68505: [PATCH v3] " Tomas Volf
2024-01-29 13:27 ` bug#68505: [PATCH v2] " 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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZbFB29cSlyL0c_mk@ws \
--to=~@wolfsden.cz \
--cc=68505@debbugs.gnu.org \
--cc=ludo@gnu.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.
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).