On Wednesday, December 07, 2011 05:38:35 PM Claudio Freire wrote:
On Wed, Dec 7, 2011 at 5:34 PM, James Oakley
wrote: SQLAlchemy has no binaries, so that doesn't change in the slightest.
If it did have binaries, they would go to /usr/local/lib/python$MAJ.$MIN/bin/ and presumably, we would have patched it to use update-alternatives to link from /usr/local/bin/.
I meant which easy_install is run.
Binaries *are* specific to a version, and it *is* required to execute binaries of a specific version in specific situations.
With alternatives, it gets really messy. With version-tagged symlinks, it's a lot cleaner.
Well, just like with Java, if you were working on Python 3, you would either: 1. Just install the python3 version, which would be set as the default, or 2. If multiple versions were installed, use update-alternatives to select the one you want, or 3. Call it as easy_install3.1. Alternatives easily supports this usage What I really don't want to see is an NIH solution, since we already have a system that packagers and users are familiar with, and is recommended by the guidelines: http://en.opensuse.org/openSUSE:Packaging_Multiple_Version_guidelines -- James Oakley jfunk@funktronics.ca -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org