From: Florian Pelz <pelzflorian@pelzflorian.de>
To: 72539@debbugs.gnu.org
Cc: "Florian Pelz" <pelzflorian@pelzflorian.de>,
"Florian Pelz" <pelzflorian@pelzflorian.de>,
"Ludovic Courtès" <ludo@gnu.org>,
"Matthew Trzcinski" <matt@excalamus.com>,
"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#72539] [PATCH] doc: Remove duplicate search paths instructions.
Date: Fri, 9 Aug 2024 13:14:36 +0200 [thread overview]
Message-ID: <70f5840b893ca2c974ee7269bdbd2e71d95bebb3.1723201995.git.pelzflorian@pelzflorian.de> (raw)
* doc/guix.texi (Invoking guix pull): Remove instructions
obsoleted by Binary Installation instructions.
Change-Id: I18274aa8bacd11de8ee72bd83c817f945468cc13
---
Being discussed in:
https://mail.gnu.org/archive/html/guix-devel/2024-08/msg00026.html
doc/guix.texi | 10 +---------
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index b7eb8fd346..5701bed871 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -4428,15 +4428,7 @@ Invoking guix pull
versa.
The result of running @command{guix pull} is a @dfn{profile} available
-under @file{~/.config/guix/current} containing the latest Guix. Thus,
-make sure to add it to the beginning of your search path so that you use
-the latest version, and similarly for the Info manual
-(@pxref{Documentation}):
-
-@example
-export PATH="$HOME/.config/guix/current/bin:$PATH"
-export INFOPATH="$HOME/.config/guix/current/share/info:$INFOPATH"
-@end example
+under @file{~/.config/guix/current} containing the latest Guix.
The @option{--list-generations} or @option{-l} option lists past generations
produced by @command{guix pull}, along with details about their provenance:
base-commit: 20dbf225f332ccc707578263ed710dcf2a8fb78e
--
2.45.2
next reply other threads:[~2024-08-09 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 11:14 Florian Pelz [this message]
2024-08-26 17:43 ` bug#72539: [PATCH] doc: Remove duplicate search paths instructions pelzflorian (Florian Pelz)
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=70f5840b893ca2c974ee7269bdbd2e71d95bebb3.1723201995.git.pelzflorian@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=72539@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=matt@excalamus.com \
--cc=maxim.cournoyer@gmail.com \
/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.