~ruther/guix-local

5dc3ce5f6c7990f44143f8e9bb9a873a014a82e4 — Ludovic Courtès 11 years ago ec2b192
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.
1 files changed, 5 insertions(+), 4 deletions(-)

M doc/guix.texi
M doc/guix.texi => doc/guix.texi +5 -4
@@ 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
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
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:

@example


@@ 297,9 300,7 @@ for instance with:

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
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
@command{guix} command.