Date: Wed, 26 Aug 1998 22:25:25 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Matthew Dillon <dillon@backplane.com> Cc: Bruce Evans <bde@zeta.org.au>, cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: src/etc make.conf Message-ID: <617.904195525@time.cdrom.com> In-Reply-To: Your message of "Wed, 26 Aug 1998 21:44:28 PDT." <199808270444.VAA10855@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> And, like rc.conf, a localization mechanism (rc.conf.local equivalent) > is required to allow the sysad to maintain his own truely local version > of the file without having to re-merge his stuff into the system-provided > make.conf every time a system update is made. > > If you want make.conf itself to be entirely local, the file should be > a nearly blank template similar to, say, /usr/src/etc/rc.local, or > not be in /usr/src/etc at all, similar to rc.conf.local. It should not > be a fairly large and complete file full of commented-out featurisms. Actually, this gets back to Paul Traina's suggestion which never really (sadly) got implemented. He proposed, some time ago, that we go to a format which listed each variable and its default value, another file being used to store the (overriding) customizations. That way you'd never suffer from having an outdated set of hooks nor would you have to merge your changes back into some central location which got wiped with each (binary) upgrade. Hmmm. Perhaps I'll just start storing the changed values into rc.conf.local from now on in sysinstall. That would sort of validate the concept. :) - Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?617.904195525>