From owner-freebsd-python@FreeBSD.ORG Sun Dec 8 21:40:01 2013 Return-Path: Delivered-To: freebsd-python@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B004DF0 for ; Sun, 8 Dec 2013 21:40:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9C15311A1 for ; Sun, 8 Dec 2013 21:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rB8Le1Zs067479 for ; Sun, 8 Dec 2013 21:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rB8Le1KU067478; Sun, 8 Dec 2013 21:40:01 GMT (envelope-from gnats) Date: Sun, 8 Dec 2013 21:40:01 GMT Message-Id: <201312082140.rB8Le1KU067478@freefall.freebsd.org> To: freebsd-python@FreeBSD.org Cc: From: Gerald Pfeifer Subject: Re: ports/184339: lang/python27 does not allow unsetting NLS (or other options) X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Gerald Pfeifer List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Dec 2013 21:40:01 -0000 The following reply was made to PR ports/184339; it has been noted by GNATS. From: Gerald Pfeifer To: bug-followup@FreeBSD.org Cc: freebsd-python@FreeBSD.org Subject: Re: ports/184339: lang/python27 does not allow unsetting NLS (or other options) Date: Sun, 8 Dec 2013 22:31:45 +0100 (CET) First of all, thanks for your thorough and helpful responses! On Thu, 28 Nov 2013, Kubilay Kocak wrote: > The WITHOUT_OPTION=yes convention is deprecated, the correct method > to customising options from the command line is: > > WITH="OPTION1 OPTIONN" or > WITHOUT="OPTION1 OPTIONN" With this change, things work for me expected, thanks. Still, even if WITHOUT_NLS is deprecated (which the system did not warn about), failing the users explicit request is not so nice. On Thu, 5 Dec 2013, John Hein wrote: > Having WITHOUT_* work in some cases but not others consistently seems > like a potential source of confusion if the rules are not spelled out > clearly. Absolutely. It definitely confused me quite a bit. :-) > As far as python27, I'm not sure why NLS is in the OPTIONS_DEFINE list > instead of just relying on the fact that NLS is a global option. As > far as I understand it, NLS could be removed from OPTIONS_DEFINE for > python27 (& other pythonXY ports). It has a slightly different > NLS_DESC than the default option, but I'm not sure that nuanced > distinction is important in this case. Unless there's a good reason > I'm missing to have NLS in OPTIONS_DEFINE, I'd vote on removing it > from OPTIONS_DEFINE in python* (and EXAMPLES and IPV6, too, I suppose). I concur. Gerald