From owner-freebsd-python@FreeBSD.ORG Sun Dec 8 21:31:57 2013 Return-Path: Delivered-To: freebsd-python@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 54A1FF62; Sun, 8 Dec 2013 21:31:57 +0000 (UTC) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) by mx1.freebsd.org (Postfix) with ESMTP id 3067F115E; Sun, 8 Dec 2013 21:31:56 +0000 (UTC) Received: from tuna.dhcp.nue.suse.com (charybdis-ext.suse.de [195.135.221.2]) by ainaz.pair.com (Postfix) with ESMTPSA id 7588B3F429; Sun, 8 Dec 2013 16:31:46 -0500 (EST) Date: Sun, 8 Dec 2013 22:31:45 +0100 (CET) From: Gerald Pfeifer To: bug-followup@FreeBSD.org Subject: Re: ports/184339: lang/python27 does not allow unsetting NLS (or other options) In-Reply-To: <21152.56398.613937.600936@gromit.timing.com> Message-ID: References: <201312051454.rB5EsC1o051327@freefall.freebsd.org> <21152.56398.613937.600936@gromit.timing.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-python@FreeBSD.org X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list 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:31:57 -0000 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