summary refs log tree commit diff
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2016-03-25 23:53:40 +0100
committerLudovic Courtès <ludo@gnu.org>2016-03-25 23:54:12 +0100
commitbf9eacd2af770c458dbd8c18d14e1885b6246313 (patch)
tree7de5ad02a07e06aa2e81e595f8a98bb2f1c12fba
parent6f773606812075ee5c6747c3b7f95285254e48f2 (diff)
downloadguix-bf9eacd2af770c458dbd8c18d14e1885b6246313.tar.gz
doc: Mention 'guix challenge' in "Features".
* doc/guix.texi (Features): Mention trust and 'guix challenge'.
-rw-r--r--doc/guix.texi5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/guix.texi b/doc/guix.texi
index 482cc9942e..b618480353 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -1264,7 +1264,10 @@ deployment}.  When a pre-built binary for a @file{/gnu/store} item is
 available from an external source---a @dfn{substitute}, Guix just
 downloads it and unpacks it;
 otherwise, it builds the package from source, locally
-(@pxref{Substitutes}).
+(@pxref{Substitutes}).  Because build results are usually bit-for-bit
+reproducible, users do not have to trust servers that provide
+substitutes: they can force a local build and @emph{challenge} providers
+(@pxref{Invoking guix challenge}).
 
 Control over the build environment is a feature that is also useful for
 developers.  The @command{guix environment} command allows developers of