From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 57910@debbugs.gnu.org, control@debbugs.gnu.org,
57909@debbugs.gnu.org, Emma Turner <em.turner@tutanota.com>
Subject: [bug#57909] bug#57910: [PATCH] Add link to 'pre-inst-env' from 'installing from git' docs
Date: Sat, 24 Sep 2022 17:58:29 +0200 [thread overview]
Message-ID: <87k05s7oii.fsf_-_@gnu.org> (raw)
In-Reply-To: <966568a4-17f7-c0f0-25a4-6f6e2928b0e7@telenet.be> (Maxime Devos's message of "Sun, 18 Sep 2022 19:26:00 +0200")
Hi,
Maxime Devos <maximedevos@telenet.be> skribis:
> As such, I think we really shouldn't recommend "make authenticate"
> (and even remove "make authenticate". In fact, I think we should
> remove "make authenticate" and replace the instructions with a direct
> "guix git authenticate ...".
“make authenticate” runs ‘guix git authenticate’ with the right
parameters; importantly, it runs the already-installed ‘guix’, not the
one in the build tree, so it’s safe (prepending “./pre-inst-env”
wouldn’t be safe as you wrote).
So I’m not sure we really need changes; WDYT?
Ludo’.
next prev parent reply other threads:[~2022-09-24 15:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 11:47 [bug#57909] Add link to 'pre-inst-env' from 'installing from git' docs Emma Turner via Guix-patches via
2022-09-18 12:41 ` [bug#57910] [PATCH] " Emma Turner via Guix-patches via
2022-09-19 9:37 ` Emma Turner via Guix-patches via
2022-09-18 14:59 ` bug#57909: Sorry - accidentally opened duplicate issues Emma Turner via Guix-patches via
2022-09-19 13:01 ` [bug#57909] " Maxime Devos
2022-09-18 17:26 ` [bug#57910] [bug#57909] Add link to 'pre-inst-env' from 'installing from git' docs Maxime Devos
2022-09-18 18:53 ` Maxime Devos
2022-09-19 6:12 ` [bug#57910] " Emma Turner via Guix-patches via
2022-09-19 13:27 ` Maxime Devos
2022-09-24 15:58 ` Ludovic Courtès [this message]
2022-09-24 16:23 ` [bug#57909] bug#57910: [PATCH] " Maxime Devos
2022-09-25 20:05 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k05s7oii.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=57909@debbugs.gnu.org \
--cc=57910@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=em.turner@tutanota.com \
--cc=maximedevos@telenet.be \
/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.