svn commit: r451109 - in head: . sysutils sysutils/iocage sysutils/py3-iocage

[Marcelo Araujo]

2017-10-03 12:01 GMT+08:00 Jan Beich <jbeich at freebsd.org>:

> Marcelo Araujo <araujo at 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.
>

We used to have py-iocage, here the CONFLICTS isn't for checking pyXY.

sysutils/iocage-devel||2017-04-10|Has expired: Outdated version. Please use
sysutils/py-iocage instead
sysutils/iocage||2017-04-10|Has expired: Outdated version. Please use
sysutils/py-iocage instead



>
> >   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 ?
>

This ports uses python3.6 and won't work with python2*


>
> >
> >   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
>


Best,
-- 

-- 
Marcelo Araujo            (__)araujo at FreeBSD.org
\\\'',)http://www.FreeBSD.org <http://www.freebsd.org/>   \/  \ ^
Power To Server.         .\. /_)