[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
branch master updated: doc: Running Guix Before It Is Installed: mention
From: |
guix-commits |
Subject: |
branch master updated: doc: Running Guix Before It Is Installed: mention ./bootstrap |
Date: |
Sun, 03 Jan 2021 17:35:59 -0500 |
This is an automated email from the git hooks/post-receive script.
niedzejkob pushed a commit to branch master
in repository guix.
The following commit(s) were added to refs/heads/master by this push:
new ad911c8 doc: Running Guix Before It Is Installed: mention ./bootstrap
ad911c8 is described below
commit ad911c832178216b0121c6ecb8349d1a9d68526f
Author: Rovanion Luckey <rovanion.luckey@gmail.com>
AuthorDate: Tue Dec 15 12:33:12 2020 +0100
doc: Running Guix Before It Is Installed: mention ./bootstrap
* doc/contributing.texi (Running Guix Before It Is Installed): Instruct
user to run ./bootstrap before ./configure.
Signed-off-by: Jakub Kądziołka <kuba@kadziolka.net>
---
doc/contributing.texi | 17 +++++++++--------
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/doc/contributing.texi b/doc/contributing.texi
index 4195cb4..d0ab083 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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- branch master updated: doc: Running Guix Before It Is Installed: mention ./bootstrap,
guix-commits <=