Subject: Re: build.sh defaults file
To: Perry E. Metzger <perry@piermont.com>
From: Ignatios Souvatzis <is@netbsd.org>
List: tech-toolchain
Date: 02/08/2003 20:24:52
--mP3DRpeJDSE+ciuQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Thu, Feb 06, 2003 at 12:08:26PM -0500, Perry E. Metzger wrote:
>=20
> 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.
>=20
> 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'm using a wrapper script (actually, one per target architecture I'm using)
for the same purpose. two lines, all of them (the first being #!/bin/sh).

Please don't add a global conf file.

Regards,
	-is
--=20
seal your e-mail: http://www.gnupg.org/

--mP3DRpeJDSE+ciuQ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (NetBSD)

iD8DBQE+RVmDPCRcZ/VMtk4RAi4MAJwKndFTiQu6W5HriC11Z3MCoJaNfQCeK5qS
PzNdwwdtD+d2/0rZHRYDtoI=
=bch9
-----END PGP SIGNATURE-----

--mP3DRpeJDSE+ciuQ--