At 15:53 -0500 3/17/00, Laird Nelson wrote:
>My curiosity is piqued by several posts recently on the subject of
>builds.
...
>
>For those of you that do run builds of your products/systems where cvs
>is the underlying version control system, how many of you:
I don't do any of your choices, exactly. For not-too-big projects, I...
1. cvs tag
2. cvs export into a new directory tree
3. use a build script in the exported directory that does:
a. all output goes to a log file created in the exported directory
b. undefines all environment vars (except USER, TZ, etc.)
c. defines all environment vars (especially PATH) that are necessary
for the build
d. cd to the starting place and make
e. create the tarball or whatever that constitutes the "product" of
this build
f. make a compressed tarball of the exported directory after the build
Note that the build script (in 3) is version controlled with the rest of
the files. It's environment definitions (in 3c) are not as good as version
controlling the OS and all the tools, but I think it's a reasonable
compromise in my environment. Step 3b is there because the unexpected
presence of "option settings" in environment variables has bit me in the
past. I keep the tarball created in 3f for as long as I think I may need to
refer to the log file (3a) or diagnose a regression test problem. It, along
with the result of step 3e sometimes become an archive on a CD.
Fred
==
Fred Brehm, Sarnoff Corporation, [EMAIL PROTECTED]
