https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234816
--- Comment #6 from Kubilay Kocak <ko...@freebsd.org> --- (In reply to gronke from comment #5) It's required for reasons of uniqueness of pkgname (distinct from the portname), because the port/package is build for a (any) particular python version, user-selectable, and will be invoked using that specific version and so for concurrent installation and conflicts (no conflicts between concurrently installable versions) reasons. Said another way, when a python package supports multiple python versions (almost all of them), then concurrently installable versions should not conflict with each other. This means using a unique package name for the same port origin built with different python versions, and using USE_PYTHON=concurrent at least, and distutils/autoplist so that installed files are not in shared/common locations, causing conflicts. If you don't want to prefix the 'portname' (and its svn dir) to be prefixed, that's fine, but I still would. On the dependency front, one should depend on the respective python ports rather than install them via pip (or any other alternate mechanism), especially since the package already appears to declare its dependencies in the correct/appropriate way (*_requires/entry_points/et al). There are plenty of python packages that only provide console_scripts/scripts, not providing importable libraries, that use all of the standard distribution/installation mechanics that the python ecosystem offers and recommends. These all end up living in the version specific python environment even if the only normal way of accessing functionality is via LOCALBASE/bin scripts. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
