[pkgsrc/trunk]: pkgsrc/doc/guide/files Some package's self-tests require a lo...

[rillig <rillig%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/efa9b07d3847
branches:  trunk
changeset: 519785:efa9b07d3847
user:      rillig <rillig%pkgsrc.org@localhost>
date:      Mon Oct 09 22:08:41 2006 +0000

description:
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:

 doc/guide/files/binary.xml |  11 ++++++++++-
 1 files changed, 10 insertions(+), 1 deletions(-)

diffs (25 lines):

diff -r 2fca3ad557d2 -r efa9b07d3847 doc/guide/files/binary.xml
--- a/doc/guide/files/binary.xml        Mon Oct 09 20:04:38 2006 +0000
+++ b/doc/guide/files/binary.xml        Mon Oct 09 22:08:41 2006 +0000
@@ -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>