Jesse Noller <jnoller@...> writes:
The reason being, is that what if I also have python 2.7 (which i do) installed, as well as python 3.1 and the release-which-will-not-be-named (3.0) - if I install that same package into one of the other versions, a new binary would be written with the same name - a script-pythonversion might also be installed, but the fact that the original script was overwritten seems broken to me.
A script is a script. What version of Python it runs with shouldn't be your (the user's) concern. Do you have two Apache binaries, one compiled with gcc 3.x and one compiled with gcc 4.x?
I think the "best" fix for this is to make the bin/ directory mirror the lib layout - each version would get it's own bin directory:
.local/ bin/ python2.6/ python3.1/
-1. The point of .local/bin is that it's (supposedly) standard, so that you have only one path to add to $PATH. Putting scripts in versioned subdirectories totally defeats its purpose.