You are not logged in.
Pages: 1
Topic closed
$ update-alternatives
bash: update-alternatives: command not found
$ pacman -Q update-alternatives
error: package "update-alternatives" not found
$ sudo pacman -Ss update-alternatives
$ #nothing found
Last edited by Doctor Drive (2010-11-09 21:04:05)
Offline
Srsly ?
Offline
This is not debian
Offline
Thanks... o__O
Offline
Hey,
So I was asking myself that same question a few weeks ago, when I noticed that Arch had switched to python 3.1 by default (broke many things on my server), and I just changed the symlink... Is that the "correct" way of doing so with Arch?
Offline
1) You've got to fix your (possibly) AUR python2 packages you have on your server, since python3 is default
2)Symlinking is not correct in any Linux distribution.
Offline
Hey flamelab,
I did point 1, I installed python2 to have a python that works with software I use, and regarding your point 2, /usr/bin/python was a symlink to python3 (IIRC), so if symlinking is not the correct way to do it, what is?
Offline
It is to point your python programs to python2 (/usr/bin/python2 or /usr/bin/env python2) not modify your system symlinks, it's wrong. Ask the devs and they will say the same.
Offline
This is really wrong, the python version dependency is supplied in setup.py, the source code shouldn't have to change for that, especially since python2 is not a standard executable across platforms, which in turn renders the multiplatform thing from python useless.
I'll keep changing symlinks, just the way update-alternatives does it, because all distros work like that...
Offline
Report that to the devs since you find that "wrong" and since "all distros work like that".
Offline
The OP has marked this solved. And, as flamelab points out, the ensuing discussion is now pointless.
Closing
Offline
Pages: 1
Topic closed