https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227573
Jan Beich <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected], | |[email protected] --- Comment #6 from Jan Beich <[email protected]> --- (In reply to Tobias C. Berner from comment #4) > ${PYTHON_PKGNAMEPREFIX}sphinx>0:textproc/py-sphinx@${PY_FLAVOR} > which will still depend on the default python flavor, but should > not fail, and just bring that in. What if a user requests different python version directly or as a dependency via another port? Obviously, the build would break due to missing sphinx-build (unsuffixed) binary. $ make -V BUILD_DEPENDS:M\*sphinx\* WITH=MANPAGES FLAVOR=py36 -C/usr/ports/devel/cmake py36-sphinx>0:textproc/py-sphinx@py36 > As this is a build-only dependency, I don't quite see > why there is a need to build it with a non-default one. Why pretend to support flavors then i.e., request flavor without BINARY_ALIAS=sphinx-build=sphinx-build-${PYTHON_VER}? Flavors are not a cargo cult, there're times when they shouldn't be used. I still think ports r460715 should be backed out to reduce complexity and fix non-default python version by explicitly not supporting it. -- You are receiving this mail because: You are the assignee for the bug.
