Date: Fri, 8 Oct 1999 19:29:43 +0200 From: Eivind Eklund <eivind@freebsd.org> To: "Daniel C. Sobral" <dcs@newsguy.com> Cc: Bruce Evans <bde@zeta.org.au>, committers@freebsd.org, arch@freebsd.org Subject: Re: /etc/make.conf abuse Message-ID: <19991008192943.S71340@bitbox.follo.net> In-Reply-To: <37FDFAE2.3A7E312B@newsguy.com> References: <199906171027.UAA03438@godzilla.zeta.org.au> <37FDFAE2.3A7E312B@newsguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 08, 1999 at 11:08:34PM +0900, Daniel C. Sobral wrote: > Bruce Evans wrote: > > Right. /etc/make.conf is for configuring make(1), not for configuring > > /usr/src. It is already abused too much for the latter. > > Can we consider stopping this abuse? It doesn't look like rocket > science to read another file for the specific purpose of configuring > /usr/src, by inserting include lines in the appropriate files at > /usr/share/mk. Perhaps I'm missing something? > > And, assuming wide opposition does not arise (though this DOES look > like a bike shed), would such a file be better located at /usr/src > or /etc? IMO: Neither. It should be located in src, whereever you check that out, so you can do several different builds with different configurations. It would be nice if it was possible to specify the name of the file on the build command line, so you could do several differently configured builds from the same source tree. I don't think this would be too difficult. In an ideal world, we would be able to do a lot more configuring of the build than today. If we want to move in that direction, it seems natural to do the entire build by doing something like # cd /usr/src # make CONFIGFILE=<configfile> buildworld # make CONFIGFILE=<configfile> installworld or similar (e.g, with a special command instead of make, and just the config file name as the parameter), and the below is written with this as a view of the world. * We would be able to add and remove parts of the build from the config file. I've added some infrastructure that should be usable for this to bsd.subdir.mk previously (with the intent of making it easier to create a configurable build) * We would be able to set variables for each part of the build, not just overall. * We would be able to build the kernel as part of the normal build (with configuration), using the build tools built as part of the world. * We would be able to re-use the parts of a previous build that matched the present configuration, to avoid having to do full rebuilds. Note that these are in an ideal world; these are by no means requirements, but moving in a direction which could eventually accomplish these would be nice. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991008192943.S71340>