From 39f8ed14374e79d1734d8651a31f492a52c44b5d Mon Sep 17 00:00:00 2001 From: Ludovic Courtès Date: Mon, 4 May 2015 14:31:00 +0200 Subject: doc: Clarify installation from the binary tarball. * doc/guix.texi (Binary Installation): Specifically refer to group/account creation, and add an item for substitutes. Mention verifiability. --- doc/guix.texi | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) (limited to 'doc') diff --git a/doc/guix.texi b/doc/guix.texi index d7868bade8..eb240b1d6b 100644 --- a/doc/guix.texi +++ b/doc/guix.texi @@ -280,8 +280,8 @@ Do @emph{not} unpack the tarball on a working Guix system since that would overwrite its own essential files. @item -Set up the daemon as explained below (@pxref{Setting Up the Daemon}), and -run it: +Create the group and user accounts for build users as explained below +(@pxref{Build Environment Setup}), and run the daemon: @example # /root/.guix-profile/bin/guix-daemon --build-users-group=guix-builder @@ -296,6 +296,14 @@ for instance with: # cd /usr/local/bin # ln -s /root/.guix-profile/bin/guix @end example + +@item +To use substitutes from @code{hydra.gnu.org} (@pxref{Substitutes}), +authorize them: + +@example +# guix archive --authorize < /root/.guix-profile/share/guix/hydra.gnu.org.pub +@end example @end enumerate And that's it! @@ -305,8 +313,8 @@ profile, or it would become subject to garbage collection---in which case you would find yourself badly handicapped by the lack of the @command{guix} command. -The tarball in question can be (re)produced simply by running the -following command in the Guix source tree: +The tarball in question can be (re)produced and verified simply by +running the following command in the Guix source tree: @example make guix-binary.@var{system}.tar.xz -- cgit v1.2.3