Satoshi Asami 8b817234de (1) Do not delete and recreate the chroot dir for every new package ... that is built. This saves a lot of time, especiall when the parallelism (the number of jobs per machine, not the number of machines) is low. However, the build script only blows away /usr/local and /usr/X11R6, so if there is a port that does some nasty things outside that area, all bets are off. (2) Better load balancing. Now, each machine reports its own load in a form of a text file, which the master merely aggregates to pick the lowest-loaded machine(s). Other than generally running faster (and more up-to-date) under loaded conditions, the master script will no longer hold up until a timeout when a machine goes down.		1999-01-26 03:06:24 +00:00
..
buildscript	Print out maintainer.	1999-01-22 09:57:16 +00:00
checkmachines	(1) Do not delete and recreate the chroot dir for every new package	1999-01-26 03:06:24 +00:00
makeduds	The scripts to allow parallel package building. See the README file in	1998-12-28 13:27:27 +00:00
makeindex	The scripts to allow parallel package building. See the README file in	1998-12-28 13:27:27 +00:00
pdispatch	The build root is now one directory up from here.	1999-01-22 10:20:32 +00:00
portbuild	(1) Do not delete and recreate the chroot dir for every new package	1999-01-26 03:06:24 +00:00
reportload	(1) Do not delete and recreate the chroot dir for every new package	1999-01-26 03:06:24 +00:00
reportload.sh	(1) Do not delete and recreate the chroot dir for every new package	1999-01-26 03:06:24 +00:00