Date: Thu, 08 Mar 2001 22:49:42 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Warner Losh <imp@village.org> Cc: (Kris Kennaway) <kris@obsecurity.org>, arch@FreeBSD.org, "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> Subject: Re: Breaking up make.conf Message-ID: <XFMail.010308224942.jhb@FreeBSD.org> In-Reply-To: <200103090354.f293sss04615@billy-club.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09-Mar-01 Warner Losh wrote: > In message <XFMail.010308193709.jhb@FreeBSD.org> John Baldwin writes: >: What if I want to use /etc/release.conf for clean release builds and >: /etc/currentworld.conf for current, etc.? If it's a tweakable variable name >: in >: /etc/make.conf (or overridable on the command line to make buildworld of >: course) then the ../Makefile.inc hack will allow me to stick this file >: anywhere >: with any name, rather than forcing it to be in the path of the source tree. > > That's why I like the idea of having a etc/make.conf in the tree and > have it use that file. This file wouldn't be checked into CVS, but > would be the user's responsibility to add to the tree in some > fashion. Given the patches I posted, they have the nice property that > if the user fails to do this, /etc/make.conf is picked up instead. I would prefer to be able to set a variable for its location so I can put it anywhwere, so as to be the most flexible. Requiring it to be higher up in the directory hierarchy at some point limits the places it can be put. > That would allow you to easily manage these things. It would also > allow you to have multiple -current and stable trees checked out under > one root and use the same config file or different config files for > them without having to remember to set special variables. Well, if you have a reasonable default, then the all-using-one-config-file case becomes very easy, because you just use the default name. You only set special variables if you want multiple config files. You could have WORLD_CONF ?= /etc/world.conf (or /etc/make/world.conf if you want a generic place for make configuration files to live) or some such. > As a side effect, we can reduce the name space polution problem that > we have with bsd.own.mk and bsd.cpu.mk being included from > /usr/share/mk/sys.mk. They have bugged me (and others) for a long > time. Yes, this would be nice. > Warner -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ 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?XFMail.010308224942.jhb>