svn commit: r559976 - in head: . deskutils/dosage devel devel/py-arrow devel/py-backports.functools_lru_cache devel/py-backports_abc devel/py-futures devel/py-graphene-sqlalchemy devel/py-jaraco.fu...

[Rene Ladan]

On Mon, Jan 04, 2021 at 01:57:59AM +0900, Yasuhiro Kimura wrote:
> From: Rene Ladan <rene at freebsd.org>
> Subject: Re: svn commit: r559976 - in head: . deskutils/dosage devel devel/py-arrow devel/py-backports.functools_lru_cache devel/py-backports_abc devel/py-futures devel/py-graphene-sqlalchemy devel/py-jaraco.fu...
> Date: Sun, 3 Jan 2021 16:25:08 +0000
> 
> > Mk/Uses/python.mk has this (line 648):
> > .if ${PYTHON_REL} < 3500
> > PY_PILLOW=      ${PYTHON_PKGNAMEPREFIX}pillow6>=6.0.0:graphics/py-pillow6@${PY_FLAVOR}
> > PY_PYGMENTS=    ${PYTHON_PKGNAMEPREFIX}pygments-25>=2.5.1<3:textproc/py-pygments-25@${PY_FLAVOR}
> > PY_SPHINX=      ${PYTHON_PKGNAMEPREFIX}sphinx18>=0,1:textproc/py-sphinx18@${PY_FLAVOR}
> > PY_TYPING=      ${PYTHON_PKGNAMEPREFIX}typing>=3.7.4.1:devel/py-typing@${PY_FLAVOR}
> > .else
> > PY_PILLOW=      ${PYTHON_PKGNAMEPREFIX}pillow>=7.0.0:graphics/py-pillow@${PY_FLAVOR}
> > PY_PYGMENTS=    ${PYTHON_PKGNAMEPREFIX}pygments>=2.5.1<3:textproc/py-pygments@${PY_FLAVOR}
> > PY_SPHINX=      ${PYTHON_PKGNAMEPREFIX}sphinx>=3.0,1:textproc/py-sphinx@${PY_FLAVOR}
> > PY_TYPING=
> > .endif
> > 
> > So it uses graphics/py-pillow on Python 3.8. But indeed if I run
> > env DEFAULT_VERSIONS=python=3.8 make -C /usr/ports/cad/k40-whisperer make describe
> > I get py-pillow6 as a dependency. The cad/k40-whisperer Makefile has
> > USES=python:-3.7 so it does not support 3.8 and 3.9, and this upper limit indeed
> > creates the py-pillow6 dependency (it works fine if you remove the -3.7 ).
> > 
> > CC'ing Mateusz as he is the maintainer of this port.
> 
> >From the viewpoint of ports framework, if a port works fine only with
> python 3.x or before and user sets 3.(x+1) or later as default
> version, how the port should behave? Should 3.x be used as dependency?
> Or should it be regareded as BROKEN or IGNORE?
> 
That is an interesting question. My gut feeling would be that such a port
should indeed be set to BROKEN or IGNORE by the framework.

René