On 12/22/05, Martin Kelly <[EMAIL PROTECTED]> wrote: > I just compiled python 2.4.2 to test out freeze (works nicely btw), and > did a "make install" figuring there would be "make uninstall" or "make > remove" but there wasn't. I captured the output of make install into a > very long text file, and it looks like it only put things in > /usr/local/bin and /usr/local/lib so I moved those somewhere else. > > The wierd thing is that running "python" now defaults to /usr/local/lib > rather than /usr/bin like it used to. I reinstalled the deb packages of > python 2.3 and python 2.4 and no use. I copied /usr/bin/python to > /usr/local/bin and it works, I'm just wondering if everything has been > remove. How can I check this?
if you've 1. erased all the files installed 2. run rehash it shouldn't be happening. item 2 causes your shell to reindex the executable files in it's $PATH if your shell is bash you ran rehash by typing '#' all by itself. you can check by running 'which python' -- http://Zoneverte.org -- information explained Do you know what your IT infrastructure does?
_______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
