[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
02/02: doc: Mention 'guix challenge' in "Features".
|
From: |
Ludovic Courtès |
|
Subject: |
02/02: doc: Mention 'guix challenge' in "Features". |
|
Date: |
Fri, 25 Mar 2016 22:54:18 +0000 |
civodul pushed a commit to branch master
in repository guix.
commit bf9eacd2af770c458dbd8c18d14e1885b6246313
Author: Ludovic Courtès <address@hidden>
Date: Fri Mar 25 23:53:40 2016 +0100
doc: Mention 'guix challenge' in "Features".
* doc/guix.texi (Features): Mention trust and 'guix challenge'.
---
doc/guix.texi | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index 482cc99..b618480 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