On Mon, May 13, 2019 at 10:05:16AM -0700, Andrew Hewus Fresh wrote:
> On Mon, May 13, 2019 at 07:37:36AM +0100, Stuart Henderson wrote:
> > As far as plists go, unless the port only supports py2 or only supports py3,
> > it ought to generate the plist with FLAVOR=python3 and then prefix any lines
> > ending in ${MODPY_PYCACHE}/ with ${MODPY_COMMENT}.
>
> I think kmos@ explained this to me correctly, but if someone wants to
> write down the why this needs to happen again I'll happily add it as a
> comment to this magic.
So this pointed out an issue to me due to this patch. As I understood
it, I could attach "${MODPY_FLAVOR}" indiscriminately to all the
depends, but this error tells me that's probably not true. Do I need to
only add the flavor if the dependent has a python3 flavor?
===> Updating plist for py3-pytest-4.5.0
Fatal: Unknown flavor(s) python3 (in devel/py-funcsigs)
(No flavors for this port). (in devel/py-funcsigs)
*** Error 1 in /usr/ports/devel/py-funcsigs
(/usr/ports/infrastructure/mk/bsd.port.mk:3564 '.BEGIN': @exit 1)
Problem with dependency STEM->=1.0:devel/py-funcsigs,python3
