From owner-freebsd-arch Sat Jun 8 19:42:19 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id CCC2237B408; Sat, 8 Jun 2002 19:42:16 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id MAA29951; Sun, 9 Jun 2002 12:42:15 +1000 Date: Sun, 9 Jun 2002 12:42:59 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Doug Barton Cc: Mike Barcroft , Subject: Re: Standardized make options (or no doesn't always mean no) In-Reply-To: <3D02AB11.F373AB4@FreeBSD.org> Message-ID: <20020609123557.X21758-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 8 Jun 2002, Doug Barton wrote: > Mike Barcroft wrote: > > > > Is anyone planning to do something about the hugely confusing state of > > NO/NO_ options? I can never remember which options have an underscore > > after the NO, so I end up writing commands like > > `make kernel ... NO_KERNELCLEAN=true NOKERNELCLEAN=true'. It would > > very nice if we could standardize this and add some compatibility > > shims for historical spellings. > > In the past versions of this conversation, the general agreement is that > going forward we should probably standardize on underscores to seperate > words. So, NO_FOO rather than NOFOO. However, no_volunteer has come > forward to do the work you've described, so if you're volunteering.... > :) On my list of things to fix after the changing the spelling of "nothing" to "no thing". :-) :-) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message