Date: Tue, 02 Nov 1999 08:53:54 -0800
From: Doug Barton <DougB@simplenet.com>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: minor heads up - /etc/make.conf{,.local} being moved
Message-ID: <381F1722.3F85DA1@simplenet.com>
References: <199910271928.MAA35915@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Dillon wrote:
>
> (Approved by jkh)
>
> /etc/make.conf.local will become /etc/make.conf and /etc/make.conf will
> become /etc/defaults/make.conf. This change is long overdue.
>
> The sys.mk adjustment has already been committed. An email has been
> sent to the CVS meisters to get /usr/src/etc/make.conf moved.
>
> make will dump out with an appropriate error and instructions if you
> update your source tree and still have an /etc/make.conf.local.
I like this change (kind of) but is it really necessary to cause make
to exit if there is a make.conf.local? Why not have it read all 3? One
of the things we talked about at the 'Con was that a three tiered system
works well for rc.conf when you have a lot of machines sharing similar
configuration details, but with some unique elements present on each
machine. Perhaps I'm missing something, but how can make.conf.local be a
bad thing?
Doug
--
"Stop it, I'm gettin' misty."
- Mel Gibson as Porter, "Payback"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?381F1722.3F85DA1>