summaryrefslogtreecommitdiff
path: root/doc/guide
diff options
context:
space:
mode:
authorrillig <rillig>2006-02-18 17:07:33 +0000
committerrillig <rillig>2006-02-18 17:07:33 +0000
commitdb31da802283a1d8f1258e43d49da846f9fd44f3 (patch)
tree2c32c889e6e68b48594d4c476ebff9aa647987f6 /doc/guide
parentcd5c93af6c6bd533a424f94bbcf1886793754d24 (diff)
downloadpkgsrc-db31da802283a1d8f1258e43d49da846f9fd44f3.tar.gz
Documented the variable ALLOW_VULNERABLE_PACKAGES to be useful for bulk
builds.
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 806dc443d47..b0d8176cef3 100644
--- a/doc/guide/files/binary.xml
+++ b/doc/guide/files/binary.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: binary.xml,v 1.21 2006/02/12 14:44:59 rillig Exp $ -->
+<!-- $NetBSD: binary.xml,v 1.22 2006/02/18 17:07:33 rillig Exp $ -->
<chapter id="binary">
<title>Creating binary packages</title>
@@ -128,6 +128,15 @@
<itemizedlist>
+ <listitem><para><varname>ALLOW_VULNERABLE_PACKAGES</varname>
+ should be set to <literal>yes</literal>. The purpose of the bulk
+ builds is creating binary packages, no matter if they are
+ vulnerable or not. When uploading the packages to a public
+ server, the vulnerable packages will be put into a directory of
+ their own. Leaving this variable unset would prevent the bulk
+ build system from even trying to build them, so possible
+ building errors would not show up.</para></listitem>
+
<listitem><para><varname>CHECK_FILES</varname>
(<filename>pkgsrc/mk/bsd.pkg.check.mk</filename>) can be set to
<quote>yes</quote> to check that the installed set of files