From owner-freebsd-arch@FreeBSD.ORG Tue Sep 9 18:03:32 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E7B116A4BF for ; Tue, 9 Sep 2003 18:03:32 -0700 (PDT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFF6C43FBF for ; Tue, 9 Sep 2003 18:03:31 -0700 (PDT) (envelope-from DougB@freebsd.org) Received: from 12-234-22-23.client.attbi.com ([12.234.22.23]) by comcast.net (sccrmhc13) with SMTP id <2003091001033001600n28vue>; Wed, 10 Sep 2003 01:03:30 +0000 Date: Tue, 9 Sep 2003 18:03:29 -0700 (PDT) From: Doug Barton To: "M. Warner Losh" In-Reply-To: <20030909.093416.91314918.imp@bsdimp.com> Message-ID: <20030909174756.M42161@12-234-22-23.pyvrag.nggov.pbz> References: <20030905.183837.116096286.imp@bsdimp.com> <20030909.093416.91314918.imp@bsdimp.com> Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-arch@freebsd.org Subject: Re: RFC: NO_FOO knobs in make.conf X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2003 01:03:32 -0000 On Tue, 9 Sep 2003, M. Warner Losh wrote: > I liked the NetBSD approach, once Bruce mentioned it, but thought I'd > wait to see what people came up with before getting into things too > much at length. Yeah, I had exactly the same feeling. I didn't want to stifle anyone's creativity. :) But since his is the best suggestion I've seen so far, and because it increases our compatibility with netbsd, I'd like to refine step one of my plan as follows: 1. All new Makefile knobs, in all branches, should have WORD_SEPARATORS between distinct English words. Internal variables should be in the form NO_FOO. In HEAD, and the eventual RELENG_5, knobs that are intended to be exposed to users should be in the form MK_FOO. Anything that isn't defined as "no" is assumed to be "yes." This gives us a lot more flexibility in terms of how we use the knobs, and how we define defaults going down the road. So for example, I'd like to have more fine grained control over what BIND bits we build, so I plan to introduce a MK_BIND_NAMED knob that controls the build of named itself, and friends like ndc. Initially I'll default this to on, but eventually I forsee switching it to off. Thoughts? Doug PS, I'll be at the tech sessions Wed-Fri if anyone wants to discuss this in person. -- This .signature sanitized for your protection