Date: Tue, 03 Oct 2017 06:01:28 +0200 From: Jan Beich <jbeich@FreeBSD.org> To: Marcelo Araujo <araujo@FreeBSD.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r451109 - in head: . sysutils sysutils/iocage sysutils/py3-iocage Message-ID: <8tgs-khgn-wny@FreeBSD.org> In-Reply-To: <201710030241.v932fWjX078115@repo.freebsd.org> (Marcelo Araujo's message of "Tue, 3 Oct 2017 02:41:32 %2B0000 (UTC)") References: <201710030241.v932fWjX078115@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Marcelo Araujo <araujo@FreeBSD.org> writes: > Author: araujo > Date: Tue Oct 3 02:41:32 2017 > New Revision: 451109 > URL: https://svnweb.freebsd.org/changeset/ports/451109 > > Log: > Rename py3-iocage to iocage as by now we don't have more conflicts with > the old iocage version If you mean CONFLICTS = py-iocage-[0-9]* then it never worked as package comparison failed on underspecificed pyXY- prefix. > and also in favor of python flavors that will land soon, it makes > sense to do it now. Wouldn't those conflict with each other unless USE_PYTHON=concurrent ? > > Sponsored by: iXsystems, Inc. > > Added: > head/sysutils/iocage/ > - copied from r451108, head/sysutils/py3-iocage/ Wasn't the python@ way to keep py- prefix in port origin to match pyXY- prefix in package name? foo/bar -> bar foo/py-bar -> py27-bar ... py36-bar foo/py2-bar -> py27-bar foo/py3-bar -> py34-bar, py35-bar, py36-bar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8tgs-khgn-wny>