explain all the client code. This readme had not been updated since

tinderbox1 days and was badly out of date.
This commit is contained in:
kestes%walrus.com 2001-12-21 19:37:54 +00:00
parent f07c70ec66
commit 6ec7e43e84

View File

@ -1,3 +1,43 @@
This directory contains code which can be used on the buildmachine. I
do not know what programs you will find most useful as this is highly
build machine dependent.
build_shellscript: A simple and general build script which you can
customize by creating a file similar to generic.sample.buildcf.
generic.sample.buildcf: a sample file to give you ideas how to build
your application.
mozilla.unix.buildcf: my best guess on how the Mozilla.org team can
use my build scripts on their builds. I really believe they should
rewrite their build scripts to have better interfaces. The complexity
does not belong in the buildscript but in their makefiles and
configure scripts.
build_redhat_initrc: an /etc/rc.d/init.d file. This is used to ensure
the build machine will start the build script after every reboot.
cull_archive_dirs: my build scripts put finished builds in an NFS
directory. I run this script every hour to keep only current builds
(the eight most recent builds and one build for each of the previous
eight days).
show_*: My build logs contain much data about the build environment.
I use these scripts to gather up the data in a readable format.
ignore_waitstatus: a program used to run other programs but ignore the
exit code. Sometimes this is useful for testing.
test_return: a test program which exits with any exit code required and
any stdout and stderr required.
This directory contains example Tinderbox client scripts. These scripts are
for illustration/documentation purposes only and are not maintained
regularly. Current scripts to build mozilla will live in an another spot