02/02: doc: Add section on installation from a binary tarball.

[Ludovic Courtès]

civodul pushed a commit to branch master
in repository guix.

commit 09722b11e5e618028051d5f6d14eb13529dc7100
Author: Ludovic Courtès <address@hidden>
Date:   Wed Apr 15 23:25:04 2015 +0200

    doc: Add section on installation from a binary tarball.
    
    * doc/guix.texi (Binary Installation): New section.
---
 doc/guix.texi |   78 ++++++++++++++++++++++++++++++++++++++++++++++++++++++---
 1 files changed, 74 insertions(+), 4 deletions(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index 1bd2a84..07ef966 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -236,20 +236,90 @@ manager, which can be done on top of a running GNU/Linux 
system.  If,
 instead, you want to install the complete GNU operating system,
 @pxref{System Installation}.
 
-The build procedure for Guix is the same as for other GNU software, and
-is not covered here.  Please see the files @file{README} and
address@hidden in the Guix source tree for additional details.
-
 @menu
+* Binary Installation::         Getting Guix running in no time!
 * Requirements::                Software needed to build and run Guix.
 * Running the Test Suite::      Testing Guix.
 * Setting Up the Daemon::       Preparing the build daemon's environment.
 * Invoking guix-daemon::        Running the build daemon.
 @end menu
 
address@hidden Binary Installation
address@hidden Binary Installation
+
+This section describes how to install Guix on an arbitrary system from a
+self-contained tarball providing binaries for Guix and for all its
+dependencies.  This is often quicker than installing from source, which
+is described in the next sections.  The only requirement is to have
address@hidden and Xz.
+
+Installing goes along these lines:
+
address@hidden
address@hidden
+Download the binary tarball from
address@hidden://alpha.gnu.org/gnu/guix/address@hidden@address@hidden
+usual, make sure to download the associated @file{.sig} file and to
+verify the authenticity of the tarball against it!}, where @var{system}
+is @code{x86_64-linux} for an @code{x86_64} machine already running the
+kernel Linux, and so on.
+
address@hidden
+As @code{root}, run:
+
address@hidden
+# cd /
+# tar xf address@hidden@var{system}.tar.xz
address@hidden example
+
+This creates @file{/gnu/store} (@pxref{The Store}), @file{/var/guix},
+and @file{/root/.guix-profile}.  @file{/root/.guix-profile} is a
+ready-to-use profile for @code{root} where Guix is installed.
+
address@hidden
+Setup the daemon as explained below (@pxref{Setting Up the Daemon}), and
+run it:
+
address@hidden
+# /root/.guix-profile/bin/guix-daemon --build-users-group=guix-builder
address@hidden example
+
address@hidden
+Make the @command{guix} command available to other users on the machine,
+for instance with:
+
address@hidden
+# mkdir -p /usr/local/bin
+# cd /usr/local/bin
+# ln -s /root/.guix-profile/bin/guix
address@hidden example
address@hidden enumerate
+
+And that's it!
+
+There are two things to note.  First, don't unpack the tarball on a
+working Guix system since that would overwrite its own essential files.
+Second, the @code{guix} package must remain available in @code{root}'s
+profile, or it would become subject to garbage collection---in which
+case you would find yourself badly handicapped by the lack of the
address@hidden command.
+
+The tarball in question can be (re)produced simply by running the
+following command in the Guix source tree:
+
address@hidden
+make address@hidden
address@hidden example
+
+
 @node Requirements
 @section Requirements
 
+This section lists requirements when building Guix from source.  The
+build procedure for Guix is the same as for other GNU software, and is
+not covered here.  Please see the files @file{README} and @file{INSTALL}
+in the Guix source tree for additional details.
+
 GNU Guix depends on the following packages:
 
 @itemize