From owner-freebsd-arch Wed Aug 30 3:41:25 2000 Delivered-To: freebsd-arch@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 02F4737B422 for ; Wed, 30 Aug 2000 03:41:21 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13U5Iy-0005UM-00; Wed, 30 Aug 2000 12:41:16 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id MAA10123; Wed, 30 Aug 2000 12:41:15 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 9778; Wed Aug 30 12:39:51 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13U5Hb-000764-00; Wed, 30 Aug 2000 12:39:51 +0200 From: Sheldon Hearn To: Alexey Zelkin Cc: arch@freebsd.org Subject: Re: NO vs NO_ In-reply-to: Your message of "Wed, 30 Aug 2000 03:26:50 MST." <200008301026.DAA50313@pike.osd.bsdi.com> Date: Wed, 30 Aug 2000 12:39:51 +0200 Message-ID: <27283.967631991@axl.fw.uunet.co.za> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexey Zelkin wrote: > looks like it's time to rehash "NO vs NO_" theme. Any objections > against changing all occurences of "NO_*" variables in src/'s Makefiles > to "NO*" ? Since "NO*" variables is mostly used in tree I think we should > go in this way to avoid lots "empty" patches. If you don't get any technical objections, make a patch available for testing and review. If the only feedback you get is about the flavour of the gravy, rather than the meat itself, listen carefully, then go ahead and do it the way you want it done. Call it "chef's prerogative". :-) For what it's worth, I agree that it'll taste better if you add underscores. In my opinion, the only technical issue worth discussing is whether the change is expected to be merged onto the RELENG_4 branch. If it's a straight conversion, you'll make life difficult for lots of people. However, if you were to put magic in the RELENG_4 mk files (when the time came), you could translate deprecated names into their new names, possibly even generating warnings for each translation. Having said that, I don't think there's any merit in providing such translation in HEAD. What you're looking for, it seems, is a clean break. A good way to do this is to allow backward compatibility in RELENG_4 but not in HEAD. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message