From owner-freebsd-arch@FreeBSD.ORG Sun Sep 7 04:02:22 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 37A7716A4C0; Sun, 7 Sep 2003 04:02:22 -0700 (PDT) Received: from amsfep12-int.chello.nl (amsfep12-int.chello.nl [213.46.243.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id C923D43FA3; Sun, 7 Sep 2003 04:02:20 -0700 (PDT) (envelope-from dodell@sitetronics.com) Received: from sitetronics.com ([213.46.142.207]) by amsfep12-int.chello.nl (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with ESMTP id <20030907110219.DVAM2869.amsfep12-int.chello.nl@sitetronics.com>; Sun, 7 Sep 2003 13:02:19 +0200 Message-ID: <3F5B1008.4010007@sitetronics.com> Date: Sun, 07 Sep 2003 13:01:28 +0200 From: "Devon H. O'Dell" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruce Evans References: <20030905140628.H90946@12-234-22-23.pyvrag.nggov.pbz> <20030907183531.V3442@gamplex.bde.org> In-Reply-To: <20030907183531.V3442@gamplex.bde.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Doug Barton 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: Sun, 07 Sep 2003 11:02:22 -0000 Regarding point 1: To me, the following would make sense: FREEBSD_IS_GOOD (in place of FREE_BSD_IS_GOOD -- FreeBSD qualifies as a word; it's a proper noun) DES_IS_OLD/3DES_IS_NEWER/RIJNDAEL_256_IS_BETTER I also don't see the point in backwards compatibility for something like this. Also, there are a few things in rc.conf that also could be separated (defaultrouter, for instance). I think if we're going to be anal about being consistent, we should be consistent through all the config files. My $0.02. --Devon 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) in the >above, BSD in FreeBSD, DES in DES, des in des, RELENG in RELENG_*, etc.? >:-> > > > >>2. Assuming that adequate volunteer resources can be found, all knobs in >>HEAD should be converted to the WORD_SEP format, and compatibility shims >>added, preferably with a suitable warning. This should happen prior to >>the 6-current branch. >> >>3. At some point in the future, the shims in 2. will be removed in >>6-current. >> >>4. The shims from 2. should probably not be removed in the eventual >>RELENG_5. (I'm open on this, I just want to be sure we get it down "on >>paper.") >> >>5. Conversion of the knobs should never be backported to RELENG_4 >> >> > >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. > >When you change this, don't forget to enforce the change on OtherBSD for >compatibility. NetBSD uses: > >%%% ># $NetBSD: bsd.README,v 1.134 2003/08/03 09:23:15 lukem Exp $ >... >NOxxx If defined, disables a feature. > Not intended for users. > This is to allow Makefiles to disable functionality > that they don't support (such as missing man pages). > NOxxx variables must be defined before > is included. >%%% > >%%% ># $NetBSD: bsd.own.mk,v 1.352 2003/08/01 22:51:34 mrg Exp $ >... ># ># Define MKxxx variables (which are either yes or no) for users ># to set in /etc/mk.conf and override in the make environment. ># These should be tested with `== "no"' or `!= "no"'. ># The NOxxx variables should only be set by Makefiles. ># > ># ># Supported NO* options (if defined, MK* will be forced to "no", ># regardless of user's mk.conf setting). ># >.for var in CRYPTO DOC HTML LINKLIB LINT MAN NLS OBJ PIC PICINSTALL PROFILE \ > SHARE >.if defined(NO${var}) >MK${var}:= no >.endif >.endfor >%%% > >Perhaps the real point here is that the mostly-implementation-detail names >for the build system leaked out to user-visible names. > >Bruce >_______________________________________________ >freebsd-arch@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-arch >To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > > > >