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.
This commit is contained in:
Ludovic Courtès 2015-05-04 14:31:00 +02:00
parent 4702cec246
commit 39f8ed1437
1 changed files with 12 additions and 4 deletions

View File

@ -280,8 +280,8 @@ Do @emph{not} unpack the tarball on a working Guix system since that
would overwrite its own essential files. would overwrite its own essential files.
@item @item
Set up the daemon as explained below (@pxref{Setting Up the Daemon}), and Create the group and user accounts for build users as explained below
run it: (@pxref{Build Environment Setup}), and run the daemon:
@example @example
# /root/.guix-profile/bin/guix-daemon --build-users-group=guix-builder # /root/.guix-profile/bin/guix-daemon --build-users-group=guix-builder
@ -296,6 +296,14 @@ for instance with:
# cd /usr/local/bin # cd /usr/local/bin
# ln -s /root/.guix-profile/bin/guix # ln -s /root/.guix-profile/bin/guix
@end example @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 @end enumerate
And that's it! 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 case you would find yourself badly handicapped by the lack of the
@command{guix} command. @command{guix} command.
The tarball in question can be (re)produced simply by running the The tarball in question can be (re)produced and verified simply by
following command in the Guix source tree: running the following command in the Guix source tree:
@example @example
make guix-binary.@var{system}.tar.xz make guix-binary.@var{system}.tar.xz