collective/buildout.python — pull request #37 by iham (2013-12-12 11:10:25+00:00)
Title: Fixed install-links to get linknames based on the named virtualenv

I wanted to change the linking a bit...

first problem was, that if you want to link a
./python-v2.4/python2.4 and a ./python-v2.4-another_venv/python2.4
both get linked as python2.4 to your /opt/local/bin; so it gets overwritten.

second i wanted to get a better naming for my links in /opt/local/bin
eg ./python-v2.4/python2.4 should link to /opt/local/bin/python-v2.4
eg ./python-v2.4/easy_install should link to /opt/local/bin/easy_install-v2.4
eg ./python-v2.4/pip should link to /opt/local/bin/pip-v2.4

i used to name my 'special' pythons by this pattern:
python-v.-
so i wanted to get
eg ./python-v2.4-someproject/python2.4 should link to /opt/local/bin/python-v2.4-someproject

third i also wanted to use activate on my shell global for each virtualenved python
eg ./python-v2.4/activate should link to /opt/local/bin/activate-v2.4

So that's what my forked install-links.in does ;)
hopefully some of you can use it!

BTW: I removed pyvenv-* from the list of files, because i don't get what to do with that...
maybe you can help ;)