path environment variables and ssh

[Ted Pavlic]

IIRC, if ssh is not logging in, it sets the PATH to some value that is 
hard-coded at compile time. I *BELIEVE* you can override this hard-coded 
path by dropping a file in your .ssh directory with your paths. The name 
of that file escapes me now.

Mercurial cannot be guaranteed to work under Python 2.3.5 as some of its 
features *require* things that are not in Python 2.3.5. That being said, 
many of its features do NOT. If you force hg to run with Py235, MOST 
LIKELY if you use a feature that needs something that Py235 doesn't 
have, "hg" is going to die. However, there's no guarantee that it will 
be "graceful" (i.e., it may happen in the MIDDLE of a commit, when 
things are half-way done, and will break your repository). In fact, 
there's no guarantee there will be an error message at all.

--Ted

James Walker wrote:
> Hi.  I'm new to mercurial, and I haven't been able to figure out where 
> to define environment variables such that they will be seen by an ssh 
> remote command to a server running Mac OS X 10.4.  For instance it's not 
> ~/.profile, which works if I log in interactively.  This caused a 
> mercurial command with an ssh URL to fail because it couldn't find hg on 
> the server.  I got around that problem by using my local .hgrc file to 
> set the remote command to /usr/local/bin/hg.  But now I'm wondering 
> about the PYTHONPATH.  If the server's hg were using python 2.3.5 (which 
> comes standard with Mac OS X 10.4) rather than python 2.5.1 (which I 
> installed), would there be an error message, or would it just run 
> suboptimally?
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
> 

-- 
Ted Pavlic <ted at tedpavlic.com>