nixo
/
guix-devel
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

doc: Warn earlier about the risk of overwriting with the binary install. 

Suggested by Pjotr Prins <pjotr.public12@thebird.nl>.

* doc/guix.texi (Binary Installation): Move warning about overwriting
  higher up.
This commit is contained in:
Ludovic Courtès 2015-04-18 22:53:54 +02:00
parent ec2b19210f
commit 5dc3ce5f6c
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/guix.texi
View File

@ -276,8 +276,11 @@ This creates @file{/gnu/store} (@pxref{The Store}), @file{/var/guix},
and @file{/root/.guix-profile}. @file{/root/.guix-profile} is a and @file{/root/.guix-profile}. @file{/root/.guix-profile} is a
ready-to-use profile for @code{root} where Guix is installed. ready-to-use profile for @code{root} where Guix is installed.
Do @emph{not} unpack the tarball on a working Guix system since that
would overwrite its own essential files.
@item @item
Setup the daemon as explained below (@pxref{Setting Up the Daemon}), and Set up the daemon as explained below (@pxref{Setting Up the Daemon}), and
run it: run it:
@example @example
@ -297,9 +300,7 @@ for instance with:
And that's it! And that's it!
There are two things to note. First, don't unpack the tarball on a The @code{guix} package must remain available in @code{root}'s
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 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.