From owner-freebsd-arch@FreeBSD.ORG Tue Sep 9 18:08:28 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 424B816A4BF for ; Tue, 9 Sep 2003 18:08:28 -0700 (PDT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B0AB43FDD for ; Tue, 9 Sep 2003 18:08:27 -0700 (PDT) (envelope-from DougB@freebsd.org) Received: from 12-234-22-23.client.attbi.com ([12.234.22.23]) by comcast.net (sccrmhc12) with SMTP id <2003091001082601200p4010e>; Wed, 10 Sep 2003 01:08:26 +0000 Date: Tue, 9 Sep 2003 18:08:25 -0700 (PDT) From: Doug Barton To: Bruce Evans In-Reply-To: <20030907183531.V3442@gamplex.bde.org> Message-ID: <20030909180341.T42161@12-234-22-23.pyvrag.nggov.pbz> References: <20030905140628.H90946@12-234-22-23.pyvrag.nggov.pbz> <20030907183531.V3442@gamplex.bde.org> 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:08:28 -0000 On Sun, 7 Sep 2003, Bruce Evans wrote: > On Fri, 5 Sep 2003, Doug Barton wrote: > > > Seems this topic is a perennial favorite, so I'd like to establish > > general agreement on a policy to deal with this going forward. I propose > > the following "guidelines" for discussion: > > > > 1. All new knobs, in all branches, should have WORD_SEPERATORS between > > distinct English words. This aids understanding of what the knob means > > for English speakers, and more importantly, those for whom English is > > not their first language. That, and actually having a standard are the > > two main reasons I'm proposing this version. > > Does this rule apply to non-English words like SEPERATORS (sic) Ooooo.... gettin' nasty with the spelling barbs, eh? Don't get me started. :) > in the above, BSD in FreeBSD, DES in DES, des in des, RELENG in > RELENG_*, etc.? :-> Hey, one thing at a time. > I won't complain much about the names of new variables, but > changing the names of old variables and adding compatibility cruft > to support 2 sets of names are wastes of time. I disagree... I think if we're going to rev the interface, we ought to do a clean sweep. Part of the reason that this topic comes up again and again is that we're massively inconistent atm. > When you change this, don't forget to enforce the change on OtherBSD for > compatibility. Heh.... just one small step in my plan for total DougBSD domination. > NetBSD uses: As commented on in the mail I just sent, I like this concept a lot, thanks for bringing it up. > Perhaps the real point here is that the mostly-implementation-detail names > for the build system leaked out to user-visible names. *nod nod* I really like the idea of having two distinct name spaces. Doug -- This .signature sanitized for your protection