01/02: doc: contributing: Clarify generating the pre-inst-env script.

[guix-commits]

efraim pushed a commit to branch master
in repository guix.

commit f4a0e472a949bfb91b85ec0612efdeabb9c60c56
Author: Efraim Flashner <efraim@flashner.co.il>
AuthorDate: Mon Sep 11 19:56:12 2023 +0300

    doc: contributing: Clarify generating the pre-inst-env script.
    
    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(-)

diff --git a/doc/contributing.texi b/doc/contributing.texi
index 4de659c7ed..ce4b9db366 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -210,12 +210,11 @@ To that end, all the command-line tools can be used even 
if you have not
 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