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

[Ben Woods]

On 3 October 2017 at 12:01, Jan Beich <jbeich at freebsd.org> wrote:

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


Given that there is only one version of iocage now, and it is not a library
that would ever be depended upon by other python programs, why does it
still need PKGNAMEPREFIX?

Now that the port is sysutils/iocage, wouldn't it make more sense for the
package to be "iocage" rather than py36-iocage?

Regards,
Ben