summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2016-02-24 22:11:41 +0100
committerLudovic Courtès <ludo@gnu.org>2016-02-24 23:24:33 +0100
commitcb05108a5d69341da9d0478c5d1609e263cc38d6 (patch)
tree2bc5f88c9b89f7dcd37d3cf54704815a02e68dfb
parent85267efb2ab6d274d6193928efaee10f97895134 (diff)
doc: Clarify who can run 'guix pull'.
Suggested by Chris Marusich <cmmarusich@gmail.com>. * doc/guix.texi (Invoking guix pull): Add paragraph explaining that any user can run 'guix pull'.
-rw-r--r--doc/guix.texi12
1 files changed, 9 insertions, 3 deletions
diff --git a/doc/guix.texi b/doc/guix.texi
index ccbab2cb30..1052f0846d 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -1992,9 +1992,15 @@ On completion, @command{guix package} will use packages and package
versions from this just-retrieved copy of Guix. Not only that, but all
the Guix commands and Scheme modules will also be taken from that latest
version. New @command{guix} sub-commands added by the update also
-become available@footnote{Under the hood, @command{guix pull} updates
-the @file{~/.config/guix/latest} symbolic link to point to the latest
-Guix, and the @command{guix} command loads code from there.}.
+become available.
+
+Any user can update their Guix copy using @command{guix pull}, and the
+effect is limited to the user who run @command{guix pull}. For
+instance, when user @code{root} runs @command{guix pull}, this has no
+effect on the version of Guix that user @code{alice} sees, and vice
+versa@footnote{Under the hood, @command{guix pull} updates the
+@file{~/.config/guix/latest} symbolic link to point to the latest Guix,
+and the @command{guix} command loads code from there.}.
The @command{guix pull} command is usually invoked with no arguments,
but it supports the following options: