From owner-freebsd-current Tue Nov 2 8:55:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt050n71.san.rr.com (dt054n7c.san.rr.com [24.30.152.124]) by hub.freebsd.org (Postfix) with ESMTP id 5CDD914BD2 for ; Tue, 2 Nov 1999 08:54:36 -0800 (PST) (envelope-from DougB@simplenet.com) Received: from simplenet.com (master [10.0.0.2]) by dt050n71.san.rr.com (8.9.3/8.8.8) with ESMTP id IAA00749; Tue, 2 Nov 1999 08:53:54 -0800 (PST) (envelope-from DougB@simplenet.com) Message-ID: <381F1722.3F85DA1@simplenet.com> Date: Tue, 02 Nov 1999 08:53:54 -0800 From: Doug Barton X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: minor heads up - /etc/make.conf{,.local} being moved References: <199910271928.MAA35915@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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