From owner-freebsd-arch Sat Jun 8 18:10:44 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mail-relay1.yahoo.com (mail-relay1.yahoo.com [216.145.48.34]) by hub.freebsd.org (Postfix) with ESMTP id 2E62537B401; Sat, 8 Jun 2002 18:10:42 -0700 (PDT) Received: from FreeBSD.org (12-234-90-219.client.attbi.com [12.234.90.219]) by mail-relay1.yahoo.com (Postfix) with ESMTP id 991B68B5B1; Sat, 8 Jun 2002 18:10:41 -0700 (PDT) Message-ID: <3D02AB11.F373AB4@FreeBSD.org> Date: Sat, 08 Jun 2002 18:10:41 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.79 [en] (X11; U; FreeBSD 4.6-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Barcroft Cc: arch@FreeBSD.ORG Subject: Re: Standardized make options (or no doesn't always mean no) References: <20020608210159.B87326@espresso.q9media.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 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.... :) -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message