From owner-svn-ports-all@freebsd.org Tue Oct 3 04:01:33 2017 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CE8BE2F9A5; Tue, 3 Oct 2017 04:01:33 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FBAA38CC; Tue, 3 Oct 2017 04:01:33 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 9A1541FC44; Tue, 3 Oct 2017 04:01:32 +0000 (UTC) From: Jan Beich To: Marcelo Araujo 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 References: <201710030241.v932fWjX078115@repo.freebsd.org> Date: Tue, 03 Oct 2017 06:01:28 +0200 In-Reply-To: <201710030241.v932fWjX078115@repo.freebsd.org> (Marcelo Araujo's message of "Tue, 3 Oct 2017 02:41:32 +0000 (UTC)") Message-ID: <8tgs-khgn-wny@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 04:01:33 -0000 Marcelo Araujo 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