summary refs log tree commit diff
path: root/doc/contributing.texi
diff options
context:
space:
mode:
authorMark H Weaver <mhw@netris.org>2015-10-20 14:11:43 -0400
committerMark H Weaver <mhw@netris.org>2015-10-20 14:11:43 -0400
commit7c6fb733e91675d1a0b80e863a422a55d1f3aa5d (patch)
treea81716c171ac75e47eed09c76e2c7de45d5de28f /doc/contributing.texi
parente38a71eea9abaa4e03ef1d7081104f93d26e31b3 (diff)
parentb1599b5299c82230722ec91dbeabcf19e3399c15 (diff)
downloadguix-7c6fb733e91675d1a0b80e863a422a55d1f3aa5d.tar.gz
Merge branch 'master' into dbus-update
Diffstat (limited to 'doc/contributing.texi')
-rw-r--r--doc/contributing.texi11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/contributing.texi b/doc/contributing.texi
index b2d097dd62..245ce9b1c4 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -234,6 +234,17 @@ For important changes, check that dependent package (if applicable) are
 not affected by the change; @code{guix refresh --list-dependent
 @var{package}} will help you do that (@pxref{Invoking guix refresh}).
 
+@item
+Check whether the package's build process is deterministic.  This
+typically means checking whether an independent build of the package
+yields the exact same result that you obtained, bit for bit.
+
+A simple way to do that is with @command{guix challenge}
+(@pxref{Invoking guix challenge}).  You may run it once the package has
+been committed and built by @code{hydra.gnu.org} to check whether it
+obtains the same result as you did.  Better yet: Find another machine
+that can build it and run @command{guix publish}.
+
 @end enumerate
 
 When posting a patch to the mailing list, use @samp{[PATCH] @dots{}} as a