diff mbox series

[bug#65871] doc: contributing: Clarify generating the pre-inst-env script.

Message ID d2afac37e499031cedc2d32e5349013dd38c3445.1694451368.git.efraim@flashner.co.il
State New
Headers show
Series [bug#65871] doc: contributing: Clarify generating the pre-inst-env script. | expand

Commit Message

Efraim Flashner Sept. 11, 2023, 4:56 p.m. UTC 
Lack of clarity reported by lrustland on IRC.

* doc/contributing.texi (Running Guix Before It Is Installed): Refer to
the Building from Git section when giving instructions for generating
the pre-inst-env script.
---
 doc/contributing.texi | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)


base-commit: 2eb6df537c36da8bf8e81ff698421f6fb1bfd1ab

Comments

Efraim Flashner Sept. 22, 2023, 8:18 a.m. UTC | #1 
Patch pushed.
diff mbox series

Patch

diff --git a/doc/contributing.texi b/doc/contributing.texi
index a0da871f1a..7651a5a2b3 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -204,12 +204,11 @@  Running Guix Before It Is Installed
 run @code{make install}.  To do that, you first need to have an
 environment with all the dependencies available (@pxref{Building from
 Git}), and then simply prefix each command with @command{./pre-inst-env}
-(the @file{pre-inst-env} script lives in the top build tree of Guix; it
-is generated by running @command{./bootstrap} followed by
-@command{./configure}).  As an example, here is how you would build the
-@code{hello} package as defined in your working tree (this assumes
-@command{guix-daemon} is already running on your system; it's OK if it's
-a different version):
+(the @file{pre-inst-env} script lives in the top build tree of Guix;
+@pxref{Building from Git} to generate it).  As an example, here is how you
+would build the @code{hello} package as defined in your working tree (this
+assumes @command{guix-daemon} is already running on your system; it's OK if
+it's a different version):
 
 @example
 $ ./pre-inst-env guix build hello