From owner-freebsd-arch Sat Oct 9 12:29:50 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 85ADD1545C for ; Sat, 9 Oct 1999 12:29:42 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id VAA10949 for ; Sat, 9 Oct 1999 21:29:39 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA53656 for freebsd-arch@freebsd.org; Sat, 9 Oct 1999 21:29:39 +0200 (MET DST) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 42A0714DB5; Sat, 9 Oct 1999 12:29:22 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id RAA18201; Sat, 9 Oct 1999 17:54:03 +0100 (BST) (envelope-from nik) Date: Sat, 9 Oct 1999 17:54:03 +0100 From: Nik Clayton To: Chuck Robey Cc: Eivind Eklund , "Daniel C. Sobral" , Bruce Evans , committers@freebsd.org, arch@freebsd.org Subject: Re: /etc/make.conf abuse Message-ID: <19991009175403.A54620@catkin.nothing-going-on.org> References: <19991008192943.S71340@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Chuck Robey on Fri, Oct 08, 1999 at 09:29:47PM -0400 Organization: FreeBSD Project Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 08, 1999 at 09:29:47PM -0400, Chuck Robey wrote: > > IMO: Neither. It should be located in src, whereever you check that > > out, so you can do several different builds with different > > configurations. It would be nice if it was possible to specify the > > name of the file on the build command line, so you could do several > > differently configured builds from the same source tree. I don't > > think this would be too difficult. > > I agree with Eivind; seeing as our make has a nice way to include files > (such as a /usr/src/make.local) One snag with that. Sometimes a remedy for fixing a build problem is # rm -rf /usr/src and start again. I know that's probably ingrained in a lot of people's fingers, and they treat /usr/src as an expendable file system. Suddenly we'll be putting a config file there. Perhaps /usr/local/etc/make.conf would be better? Or at least a variable (which can be defined in /etc/make.conf) which points to the file, so that the admin can easily set local policy. N -- PS: Sorry for the delay in replying. What with work, buying a house, moving in to the house, fixing the plumbing in the house, and paying the bills, I've been a little busy recently. I'm back to e-mail now, and catching up. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message