Danke Diez, easy_install without 'install' works better :-) .
As as you indicated: Virtualenv installs cleanly in a separate directory named virtualenv-1.3.3-py2.5.egg, So I removed the --prefix option and installed it in the default path. By the way: Adding the word 'install' wasn't inspired by apt-get, but by "python ./setup.py", which also seems to want a 'command' bye N Diez B. Roggisch wrote: > News123 wrote: > >> Hi Alex, >> >> >> Thanks a lot. Reading the description this sounds to be the right thing. >> >> >> But now I'm stuck installing virtualenv as a user as this seems to be no >> ubunbtu package: >> >> >> export PYTHONPATH=/opt/newpymod/lib/python2.5/site-packages >> mkdir -p $PYTHONPATH >> easy_install --prefix /opt/newpymod install virtualenv > > Just because apt-get uses "install" as command doesn't mean everything else > does. And easy_install is one of those which doesn't. Remove the "install", > and things should work. > > Additionally, I don't see any problem with installing virtualenv into the > system-python. It's an addon, not a replacement, thus it shouldn't collide > with package management (unless you are going to remove python) > > Diez -- http://mail.python.org/mailman/listinfo/python-list
