From fa6aec177e1b3f67cda57938665e27e30bad0cf9 Mon Sep 17 00:00:00 2001 From: dmcmahill Date: Sat, 14 Apr 2001 19:20:47 +0000 Subject: document the possibility of a pre-build.local file for bulk builds --- Packages.txt | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) (limited to 'Packages.txt') diff --git a/Packages.txt b/Packages.txt index 4aead84edee..a8e75b202f1 100644 --- a/Packages.txt +++ b/Packages.txt @@ -1,4 +1,4 @@ -# $NetBSD: Packages.txt,v 1.148 2001/03/29 11:20:57 agc Exp $ +# $NetBSD: Packages.txt,v 1.149 2001/04/14 19:20:47 dmcmahill Exp $ ########################################################################### ========================== @@ -351,6 +351,20 @@ file that determines where logfiles are generated after the build, where to mail the build report, where your pkgsrc is located and which user to su(8) to to do a 'cvs update'. + 3.2.1.3 pre-build.local + ======================= + +It is possible to configure the bulk build to perform certain site +specific tasks at the end of the pre-build stage. If the file +``pre-build.local'' exists in pkgsrc/mk/bulk it will be executed +(as a sh(1) script) at the end of the usual pre-build stage. An +example use of pre-build.local is to have the line: + + echo "I do not have enough disk space to build this pig." \ + > games/crafty-book-enormous/$BROKENF + +to prevent the system from trying to build a particular package +which requires nearly 3 Gb of disk space. 3.2.2 Other environmental considerations ======================================== -- cgit v1.2.3