From owner-svn-ports-head@FreeBSD.ORG Sun Aug 10 23:36:26 2014 Return-Path: Delivered-To: svn-ports-head@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 CAB26A54; Sun, 10 Aug 2014 23:36:26 +0000 (UTC) Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7DD8A2D6D; Sun, 10 Aug 2014 23:36:26 +0000 (UTC) Received: by mail-pd0-f170.google.com with SMTP id g10so9819715pdj.29 for ; Sun, 10 Aug 2014 16:36:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=dnl6YUYfs7U/UmRCE3JslBKyHEHQAmSJBbL+1XbHM4U=; b=LVQysvd9gzVzQsinJO2+K4CrSOQzRPxkmN2aEeFbce1t02eW2owAcxakg3u118VFM5 VG8JU20KwAUjzqSmrvlpygt+4vM7QwQJxtQRV/CNpgFx5HnuSwbEQ3wMM45p/0jOppyx Ivnv7/564n3i/9qZ1pfkhvO+30MAxCz6gdxlViA9tETFoMQPZoSk8IuXXiULMoDGr97W yLJSLdsts/Xuf3vngsMtXGuSgxtU44r/5QqUnMY+NcQDK8JzERFVt0lW1+AtCtl50cTU 2JrqBJy/9yBO5h74Lfo73/nYFb4nBHDOmUZohECNhaKjh9AJTqodUx85T/XUvsij3Jsz YKsQ== X-Received: by 10.70.36.239 with SMTP id t15mr19770739pdj.83.1407713785998; Sun, 10 Aug 2014 16:36:25 -0700 (PDT) Received: from ?IPv6:2001:44b8:31ae:7b00:898d:2993:e1fd:8220? (2001-44b8-31ae-7b00-898d-2993-e1fd-8220.static.ipv6.internode.on.net. [2001:44b8:31ae:7b00:898d:2993:e1fd:8220]) by mx.google.com with ESMTPSA id pd1sm6108668pdb.76.2014.08.10.16.36.23 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 10 Aug 2014 16:36:25 -0700 (PDT) Sender: Kubilay Kocak Message-ID: <53E801F5.1000403@FreeBSD.org> Date: Mon, 11 Aug 2014 09:36:21 +1000 From: Kubilay Kocak Reply-To: koobs@FreeBSD.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Marcus von Appen Subject: Re: svn commit: r364518 - in head: accessibility/py-papi audio/py-al devel/py-astroid devel/py-dynrules devel/py-game devel/py-logilab-common devel/py-ocempgui devel/py-ply devel/py-sdl2 devel/pychecke... References: <53e7336d.2c4d.2257f090@svn.freebsd.org> <20140810095516.GA35955@FreeBSD.org> <2556564.WKGpsAPjlp@mercury.ph.man.ac.uk> <20140810155649.GA1040@medusa.sysfault.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: svn-ports-head@freebsd.org, Max Brazhnikov , Alexey Dokuchaev , svn-ports-all@freebsd.org, ports-committers@freebsd.org, Adam Weinberger X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Aug 2014 23:36:27 -0000 On 11/08/2014 2:40 AM, Adam Weinberger wrote: > On 10 Aug, 2014, at 11:56, Marcus von Appen wrote: > >> On, Sun Aug 10, 2014, Max Brazhnikov wrote: >> >>> On Sun, 10 Aug 2014 09:55:16 +0000 Alexey Dokuchaev wrote: >>>> On Sun, Aug 10, 2014 at 08:55:08AM +0000, Marcus von Appen wrote: >>>>> New Revision: 364518 >>>>> URL: http://svnweb.freebsd.org/changeset/ports/364518 >>>>> QAT: https://qat.redports.org/buildarchive/r364518/ >>>>> >>>>> -USES= pkgconfig >>>>> +USES= pkgconfig python:2 >>>>> USE_GNOME= atk >>>>> -USE_PYTHON= 2 >>>>> -USE_PYDISTUTILS=yes >>>>> -PYDISTUTILS_AUTOPLIST= yes >>>>> +PYTHON_FEATURES=autoplist distutils >>>> >>>> Yuck, this PYTHON_FEATURES knob is ugly. Why not follow Perl's example >>>> instead (USES=perl and USE_PERL)? It both makes more sense and shorter. >>> >>> ugly or not, it's a matter of taste. But PYTHON_FEATURES usage is inconsistent >>> with COMPILER_FEATURES (read only var). Could we rename it while it's not too late? >> >> Using USE_PYTHON is a problem, since this would be inconsistent with many >> other parts of the infrastructure. Aside from that, it would need a lot of >> glue code for the transition phase. >> >> Regardless of that, if portmgr's common suggestion is that XXX_FEATURES is >> about testing for a certain feature (read-only), I'm fine with it and open for >> suggestions, which describe that infrastructure bit X wants to enable a >> certain infrastructure feature. >> >> PYTHON_FEATURES is in my opinion the best by far. If the consensus is to use >> USE_PYTHON, similar to USE_PERL5, this will require us to migrate all python >> ports from USE_PYTHON to USES=python first and will take some time. > > Can it just treat USE_PTYHON as PYTHON_FEATURES if USES=python is defined? Marcus, how feasible is this (minus the typo) to make the transition without a mass conversion first-phase? I like the idea of USE_FOO=bar[:baz]<,qux> being the canonical convention for easy transfer of existing knowledge for maintainers (perl -> python -> *) Koobs