summaryrefslogtreecommitdiff
path: root/doc/guide
diff options
context:
space:
mode:
authorrillig <rillig@pkgsrc.org>2006-10-09 22:08:41 +0000
committerrillig <rillig@pkgsrc.org>2006-10-09 22:08:41 +0000
commitec77758bec648897bb46f25845b99b6c39d13094 (patch)
tree38a0d9f3be44c43412ea3881b89e16a336d18864 /doc/guide
parentbf486336c3e1003c8e9c3b6794f787a4a008dcae (diff)
downloadpkgsrc-ec77758bec648897bb46f25845b99b6c39d13094.tar.gz
Some package's self-tests require a lot of high-quality random data, so
the bulk build may seem to hang on otherwise idle machines.
Diffstat (limited to 'doc/guide')
-rw-r--r--doc/guide/files/binary.xml11
1 files changed, 10 insertions, 1 deletions
diff --git a/doc/guide/files/binary.xml b/doc/guide/files/binary.xml
index d3ec0b82775..90e43322601 100644
--- a/doc/guide/files/binary.xml
+++ b/doc/guide/files/binary.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: binary.xml,v 1.26 2006/09/10 19:51:49 wiz Exp $ -->
+<!-- $NetBSD: binary.xml,v 1.27 2006/10/09 22:08:41 rillig Exp $ -->
<chapter id="binary">
<title>Creating binary packages</title>
@@ -144,6 +144,15 @@
<quote>#!</quote>-scripts will find their
interpreter.</para></listitem>
+ <listitem><para><varname>PKGSRC_RUN_TEST</varname> can be set
+ to <quote><literal>yes</literal></quote> to run each package's
+ self-test before installing it. Note that some packages make
+ heavy use of <quote>good</quote> random numbers, so you need
+ to assure that the machine you are doing the bulk builds is
+ not completely idle. Otherwise some test programs will seem to
+ hang, while they are just waiting for new random data to be
+ available.</para></listitem>
+
</itemizedlist>
</sect3>