From: swedebugia <swedebugia@riseup.net>
To: 33385@debbugs.gnu.org, guix@lprndn.info
Subject: [bug#33385] [PATCH] doc: Modify sentence to clarify that ./pre-inst-env is generated
Date: Wed, 14 Nov 2018 20:09:34 +0100 [thread overview]
Message-ID: <6294c779-ea5e-2998-b955-2eb48c5d095e@riseup.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 23 bytes --]
--
Cheers
Swedebugia
[-- Attachment #2: 0001-doc-Modify-sentence-to-clarify-that-.-pre-inst-env-i.patch --]
[-- Type: text/x-patch, Size: 2072 bytes --]
From ce93cbc8ce4c3cba59cf70c8d073af0a796935ec Mon Sep 17 00:00:00 2001
From: swedebugia <swedebugia@riseup.net>
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
-@command{./pre-inst-env} (the @file{pre-inst-env} script lives in the
-top build tree of Guix), as in@footnote{The @option{-E} flag to
-@command{sudo} 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.}:
+@cindex pre-inst-env
+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 is generated during the bootstrapping and configuring of Guix and is
+located in the top build tree of Guix), as in@footnote{The @option{-E} flag to
+@command{sudo} 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
next reply other threads:[~2018-11-14 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 19:09 swedebugia [this message]
2018-11-16 22:17 ` bug#33385: [PATCH] doc: Modify sentence to clarify that ./pre-inst-env is generated Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6294c779-ea5e-2998-b955-2eb48c5d095e@riseup.net \
--to=swedebugia@riseup.net \
--cc=33385@debbugs.gnu.org \
--cc=guix@lprndn.info \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).