Move path definitions forward in _bashrc
authorW. Trevor King <wking@drexel.edu>
Tue, 1 Jun 2010 17:46:06 +0000 (13:46 -0400)
committerW. Trevor King <wking@drexel.edu>
Tue, 1 Jun 2010 17:46:06 +0000 (13:46 -0400)
commit9c41afb6929cc7949ae011929d25bdd5837dde17
tree819cf6d475827d3772d9fe0debfc1859fa965849
parent8559a2f48fd4ab192fedb2d77062ec386335a063
Move path definitions forward in _bashrc

This way they are defined even for non-interactive sessions.  An
example where this is necessary is for the target of an
  hg push ssh://...

Where you can't install Mercurial systemwide on the target.  Mercurial
logs in using ssh without setting up a prompt, but we still need to
define a PATH and PYTHONPATH including the Mercurial install
locations:
  ~/bin/hg
  ~/lib/python2.5/site-packages/mercurial-1.5.3-py2.5-linux-i686.egg/
Actually, the .egg directory is added in
  ~/lib/python2.5/site-packages/easy-install.pth
So we only need
  ~/lib/python2.5/site-packages/
in our PYTHONPATH.
_bashrc