[ 16:37 flz  ]

• 1.2 Tools/portbuild/conf/.cvsignore
• 1.2 Tools/portbuild/conf/README.dotunnel
• 1.5 Tools/portbuild/conf/client.conf
• 1.2 Tools/portbuild/conf/common.conf
• 1.2 Tools/portbuild/conf/make.conf
• 1.8 Tools/portbuild/conf/server.conf
• 1.19 Tools/portbuild/errorlogs/index.shtml
• 1.2 Tools/portbuild/mlist
• 1.7 Tools/portbuild/portbuild.conf
• 1.7 Tools/portbuild/scripts/allgohans

Remove portbuild scripts from pcvs, as they now live in svn/projects.

[ 22:49 linimon  ]

• 1.10 Tools/portbuild/scripts/buildfailure
• 1.11 Tools/portbuild/scripts/buildsuccess
• 1.13 Tools/portbuild/scripts/claim-chroot
• 1.11 Tools/portbuild/scripts/cleanup-chroots
• 1.2 Tools/portbuild/scripts/client-metrics
• 1.4 Tools/portbuild/scripts/flushsquid
• 1.3 Tools/portbuild/scripts/keeprestr
• 1.25 Tools/portbuild/scripts/makeduds
• 1.22 Tools/portbuild/scripts/mkbindist
• 1.7 Tools/portbuild/scripts/prunefailure

Generalize the packge building scripts to be able to be run on more than
one 'head' node, rather than just pointyhat itself.

Constants are factored out into installation-specific files known as
portbuild/conf/server.conf and portbuild/conf/client.conf.  There is
only one server.conf file.  Individual <arch> directories may have
their own client.conf files, or may symlink to ../conf/client.conf.

This first set of files only gets the *.conf files and some cleanup.

Feature safe:   yes

[ 08:58 kris  ]

• 1.3 Tools/portbuild/scripts/flushsquid

Don't require an /etc/arch file, we can obtain the information from uname

[ 04:42 kris  ]

• 1.2 Tools/portbuild/scripts/flushsquid

The squid rc.d script no longer has the .sh suffix

[ 04:41 kris  ]

• 1.1 Tools/portbuild/scripts/flushsquid

This script may be run on a client machine to force it to flush its squid
cache.  This is useful if the client is holding a bad or stale cached
copy of a package that is causing problems for package builds.