I was trying to a BDEPEND block that would be more easily maintainable where dependency have to match the version of the current package in my overlay (sage-on-gentoo). My block was as follow BDEPEND="$(python_gen_any_dep ' >=dev-python/sphinx-4.1.0[${PYTHON_USEDEP}] ~sci-mathematics/sage-${PV}[${PYTHON_USEDEP},jmol] ~sci-mathematics/sage_docbuild-${PV}[${PYTHON_USEDEP}] ')" This was rejected when run through repoman with [INFO] checking package sci-mathematics/sage-doc dependency.syntax [fatal] 2 sci-mathematics/sage-doc/sage-doc-9999.ebuild: BDEPEND: Invalid atom (~sci-mathematics/sage-${PV}[python_targets_python3_9(-),jmol]), token 6 sci-mathematics/sage-doc/sage-doc-9999.ebuild: BDEPEND: Invalid atom (~sci-mathematics/sage-${PV}[python_targets_python3_9(-),jmol]), token 6 Please fix these important QA issues first. == Replacing ${PV} by explicit values did go through. Using ${PV} in `python_check_deps` did not result in any issues as it got properly expanded there. Variables such as ${PV} should be properly expanded in `python_den_any_dep` if it is possible. Reproducible: Always
I think this may work if you use double quotes and then escape: https://dev.gentoo.org/~mgorny/python-guide/buildsys.html#single-impl-package
(In reply to Sam James from comment #1) > I think this may work if you use double quotes and then escape: > https://dev.gentoo.org/~mgorny/python-guide/buildsys.html#single-impl-package Does work! Thanks for the style assist Sam. I totally didn't see that example later in the manual.
