>From ce93cbc8ce4c3cba59cf70c8d073af0a796935ec Mon Sep 17 00:00:00 2001 From: swedebugia Date: Wed, 14 Nov 2018 20:03:57 +0100 Subject: [PATCH] doc: Modify sentence to clarify that ./pre-inst-env is generated * doc/contributing.texi (Running Guix Before It Is Installed): Modify --- doc/contributing.texi | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/doc/contributing.texi b/doc/contributing.texi index 91a87ef2d..6d66d7eed 100644 --- a/doc/contributing.texi +++ b/doc/contributing.texi @@ -107,15 +107,16 @@ test the changes made in your local source tree checkout without 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 address@hidden/pre-inst-env} (the @file{pre-inst-env} script lives in the -top build tree of Guix), as address@hidden @option{-E} flag to address@hidden guarantees that @code{GUILE_LOAD_PATH} is correctly set -such that @command{guix-daemon} and the tools it uses can find the Guile -modules they need.}: address@hidden pre-inst-env +To that end, all the command-line tools can be used even if you have not run address@hidden 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 is generated during the bootstrapping and configuring of Guix and is +located in the top build tree of Guix), as address@hidden @option{-E} flag to address@hidden guarantees that @code{GUILE_LOAD_PATH} is correctly set such +that @command{guix-daemon} and the tools it uses can find the Guile modules +they need.}: @example $ sudo -E ./pre-inst-env guix-daemon --build-users-group=guixbuild -- 2.18.0