Date: Mon, 31 Aug 2015 06:27:49 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Kubilay Kocak <koobs@FreeBSD.org> Cc: Thomas Zander <riggs@freebsd.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r395628 - in head/www: . py-pyocclient Message-ID: <20150831062749.GA56296@FreeBSD.org> In-Reply-To: <55E3EF7B.2010404@FreeBSD.org> References: <201508301655.t7UGtEVx037588@repo.freebsd.org> <55E3CED6.3010703@FreeBSD.org> <CAFU734xKRBuFNQTKvb59v0eK4qmzFHwZiWWUBqahG5G5SJXyXw@mail.gmail.com> <55E3E915.7060300@FreeBSD.org> <20150831055703.GA44646@FreeBSD.org> <55E3EF7B.2010404@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 31, 2015 at 04:08:59PM +1000, Kubilay Kocak wrote: > On 31/08/2015 3:57 PM, Alexey Dokuchaev wrote: > > On Mon, Aug 31, 2015 at 03:41:41PM +1000, Kubilay Kocak wrote: > >> Ports should be declarative rather than imperative in respect to > >> describing what Python versions are supported. > >> > >> I'm not 100% sure whether USES=python supports the a.b,a.c format > >> (I don't think it does), but if not, the closest thing we have to > >> stipulating "< a.d" is "-a.c". > > > > If "port only supports 2.x" what's more declaratively clear than > > python:2? > > python:2 unfortunately implicitly means 'depend on the lang/python2' > metaport, "not any version of 2.x" Oh, that's unfortunate indeed (I was always wondering about those meta ports and why do I have installed both python2-2_3 and python27-2.7.10). Are there plans to get rid of this complexity? (I'm not quoting the rest of your mail as I don't have anything to say; you probably know what you guys're [will be] doing about this. :) ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150831062749.GA56296>