Re: bin/pip3.12 or bin/pip-3.12

[Thomas Klausner <wiz%gatalith.at@localhost>]

On Thu, May 08, 2025 at 04:41:31PM +0200, Dr. Thomas Orgis wrote:
> In this case I'd argue that it doesn't make sense to build ALPS
> multiple times for differing pythons. You'd need to teach dependent
> packages (which is DIRAC, in my case) about funky renamed binaries
> (programs and libraries, headers). I don't really see that happening.

We have packages like that too, e.g. devel/meld. It's a Python
program, but there is no point in installing it multiple times.

> But to the point, if I werer to package ALPS, would you prefer to have
> it named science/py-alps (remembering a discussion about category names
> some time ago … ) with all the python naming stuff and
> PYTHON_SELF_CONFLICT or rather have it as non-versioned science/alps
> with

Probably science/alps

> PYTHON_VERSIONS_ACCEPTED=  ${PYTHON_VERSION_DEFAULT}
> 
> ?

Without this. Why limit it to the default accepted version?
It will only be built once anyway.

> I must admit, though, that I begin to question my choice to build
> several versions of python3 for our users in one pkgsrc tree. Maybe the
> time has come at some point to reduce that number to 1 again … now since
> python2 is just barely rocking on the deathbed.

Python3 have been quite interoperable for me, though ISTR that there
were problems from 3.7? to 3.8? (both no longer in pkgsrc).
 Thomas