On Thu, Feb 06, 2003 at 02:20:12PM -0500, Nathan Williams wrote:
  | "Perry E. Metzger" <perry@piermont.com> writes:
  | 
  | > 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.)
  | 
  | I hate global configuration files for tools. They're a hidden
  | dependancy on system state, and they tend to bite me when
  | another user uses the system or I want to do a "plain" build.

I fully agree with Nathan.

/etc/build.conf (or even "./build.conf" relative to "build.sh")
is unnecessary.

Luke.