diff options
author | joerg <joerg@pkgsrc.org> | 2008-04-04 18:31:25 +0000 |
---|---|---|
committer | joerg <joerg@pkgsrc.org> | 2008-04-04 18:31:25 +0000 |
commit | 27238fd52520be865ae6989f3602be02ec8cf1f7 (patch) | |
tree | 40cb54edc079d8c9c53567928161625afdabcec2 | |
parent | 45a66a4a021019f4ef41afdf3315583ae372a3bc (diff) | |
download | pkgsrc-27238fd52520be865ae6989f3602be02ec8cf1f7.tar.gz |
Add a note about sharing sandboxes between master and slave based on
discussion with Havard. Add a reference to the bulkbuild-restart script.
-rw-r--r-- | doc/HOWTO-pbulk | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/HOWTO-pbulk b/doc/HOWTO-pbulk index 21d84b55f5d..2771a5c8f0a 100644 --- a/doc/HOWTO-pbulk +++ b/doc/HOWTO-pbulk @@ -13,6 +13,10 @@ For parallel builds, /bulklog, /packages and /usr/pkgsrc are supposed to 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 @@ Step Four: Running pbulk 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 |