On Thu, Feb 06, 2003 at 12:08:26PM -0500, Perry E. Metzger wrote:

 > A lot of the time, I use the same arguments to build.sh to set
 > defaults over and over again -- things that I do not want in my
 > /etc/mk.conf file or which cannot be set in an mk.conf file.
 > 
 > I am thinking of adding an /etc/build.conf file to the system that
 > would get slurped in by build.sh if it existed -- this file could
 > export a bunch of variables to control build.sh behavior. (The change
 > is two lines.)

This is totally ridiculous.  Another random config file for something
which can be handled with a shell alias or a wrapper script.

Considering how totally unnecessary it is, and how there are other ways
to skin the cat, my inclination is "no".

-- 
        -- Jason R. Thorpe <thorpej@wasabisystems.com>