[pkgsrc/trunk]: pkgsrc/doc Add a note about sharing sandboxes between master ...

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

details:   https://anonhg.NetBSD.org/pkgsrc/rev/ffc89fbce44f
branches:  trunk
changeset: 540601:ffc89fbce44f
user:      joerg <joerg%pkgsrc.org@localhost>
date:      Fri Apr 04 18:31:25 2008 +0000

description:
Add a note about sharing sandboxes between master and slave based on
discussion with Havard. Add a reference to the bulkbuild-restart script.

diffstat:

 doc/HOWTO-pbulk |  8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)

diffs (25 lines):

diff -r 5167f1715a37 -r ffc89fbce44f doc/HOWTO-pbulk
--- a/doc/HOWTO-pbulk   Fri Apr 04 18:24:47 2008 +0000
+++ b/doc/HOWTO-pbulk   Fri Apr 04 18:31:25 2008 +0000
@@ -13,6 +13,10 @@
 be shared (null mounts, NFS). /usr/pkg and /var/db/pkg needs to be
 per-node and /scratch should be per-node.
 
+The defaults scripts will remove /usr/pkg and /var/db/pkg on the master
+node as well. When using chroot sandboxes for the build, the master can
+share a sandbox with one of the build instances.
+
 Step Two: Preparing pbulk prefix
 
 Install pkgtools/pbulk and possibly helper programs like screen into
@@ -55,6 +59,10 @@
 individual build phases. They depend on the execution of the phase
 before. Exceptions are report and upload which both depend on build.
 
+/usr/pkg_bulk/bin/bulkbuild-restart can be used to resume an aborted
+build. If it failed after the actual build phase, report and upload should
+be called individually though.
+
 --- sample mk.conf fragment ---
 
 WRKOBJDIR = /scratch