From bf9eacd2af770c458dbd8c18d14e1885b6246313 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= Date: Fri, 25 Mar 2016 23:53:40 +0100 Subject: [PATCH] doc: Mention 'guix challenge' in "Features". * doc/guix.texi (Features): Mention trust and 'guix challenge'. --- doc/guix.texi | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) 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