From owner-freebsd-ports@FreeBSD.ORG Mon Jun 4 20:48:11 2012 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id D793B106567B; Mon, 4 Jun 2012 20:48:11 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id DFEF51578A5; Mon, 4 Jun 2012 20:47:03 +0000 (UTC) Message-ID: <4FCD1EC7.9060905@FreeBSD.org> Date: Mon, 04 Jun 2012 13:47:03 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120506 Thunderbird/12.0.1 MIME-Version: 1.0 To: Baptiste Daroussin X-Enigmail-Version: 1.5pre OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD ports list Subject: NO_OPTIONS_SORT makes options disappear X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 20:48:12 -0000 The new options framework sorts all of the options by default before presenting them to the user. I have mixed feelings about this, however there is supposed to be a workaround for those of us who have grouped the options for our ports into logical chunks, NO_OPTIONS_SORT. Today I tried defining that in my BIND ports so that users would not be confused during the upgrade process, and got this: make config ===> No options to configure I tried defining NO_OPTIONS_SORT both before and after including bsd.port.pre.mk, got the same result for both. Suggestions welcome, Doug -- This .signature sanitized for your protection