From owner-cvs-all Sat Aug 29 15:00:58 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10611 for cvs-all-outgoing; Sat, 29 Aug 1998 15:00:58 -0700 (PDT) (envelope-from owner-cvs-all) Received: from veda.is (veda.is [193.4.230.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10602 for ; Sat, 29 Aug 1998 15:00:53 -0700 (PDT) (envelope-from adam@veda.is) Received: (from adam@localhost) by veda.is (8.9.0/8.9.0) id VAA00393; Sat, 29 Aug 1998 21:59:48 GMT From: Adam David Message-Id: <199808292159.VAA00393@veda.is> Subject: Re: make.conf In-Reply-To: <199808292024.OAA03092@harmony.village.org> from Warner Losh at "Aug 29, 98 02:24:24 pm" To: imp@village.org (Warner Losh) Date: Sat, 29 Aug 1998 21:59:47 +0000 (GMT) Cc: committers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-cvs-all@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In message <199808291735.RAA24925@veda.is> Adam David writes: > : How about /etc/make/{ports,src}.conf or similar. I forgot to mention also /etc/make/bmake.conf to replace /etc/make.conf as included in sys.mk. Perhaps sys.conf would also be useful to separate out kernel specific parameters. > What's the mechanism that you'd accomplish this by? Right now it is > very easy to have sys.mk include /etc/make.conf, but it isn't very > right. bsd.port.mk is used to build ports, so ports.conf could be included there. If there is no suitable bsd.*.mk for including src.conf then arrange things so there is a corresponding bsd.src.mk or equivalent mechanism for including src.conf. -- Adam David