[PATCH] Added detail to instructions on generating pre-inst-env

[Rovanion Luckey <rovanion.luckey@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 224 bytes --]

Hi,
First time patcher. I only got Gmail as a mail client set up until I can
get mu4e running in Guix so I hope it can manage to not munge attached
patchfiles. The patch only adds a part of a sentence I thought was missing.

[-- Attachment #1.2: Type: text/html, Size: 271 bytes --]

[-- Attachment #2: 0001-doc-contributing-Added-detail-to-instructions-on-gen.patch --]
[-- Type: text/x-patch, Size: 1971 bytes --]

From 73c8fc9a070e14e9155065512ca4150b26d4e86a Mon Sep 17 00:00:00 2001
From: Rovanion Luckey <rovanion.luckey@gmail.com>
Date: Tue, 15 Dec 2020 12:33:12 +0100
Subject: [PATCH] doc: contributing: Added detail to instructions on generating
 pre-inst-env

The file ./configure does not exist before the new developer runs ./bootstrap.
---
 doc/contributing.texi | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/doc/contributing.texi b/doc/contributing.texi
index 78d9990b30..316caea16c 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -166,14 +166,15 @@ actually installing them.  So that you can distinguish between your
 ``end-user'' hat and your ``motley'' costume.
 
 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 @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):
+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):
 
 @example
 $ ./pre-inst-env guix build hello
-- 
2.29.2