Allan Clark wrote: > Juliusz Chroboczek wrote: >>> But if you don't have the ability to change the default path (or move >>> the darcs executable into it) then this basically means you know what >>> the problem is but you can't solve it. >>> In my case I shouted (okay asked politely) at support but was met >>> with "no" >>> >> >> Allan, >> >> You don't need to have darcs in the system default path; you only need >> to have it in your personal default path. >> >> Assuming you're using bash, the following should do the trick: >> >> $ mkdir ~/bin/ >> $ mv darcs ~/bin/ >> $ echo 'PATH="$HOME/bin:$PATH"' >> ~/.bashrc >> >> Juliusz >> > Oh yes this is already in my ~/.bashrc, otherwise I wouldn't be able to > run darcs when normally logged in (ie. when I am actually at work). The > problem is that a non-interactive shell doesn't run ~/.bashrc (at least > not on the setup here). > So basically I: > a) Couldn't seem to change the default path for a non-interactive remote > login > b) couldn't install darcs in what is the default path ... > > It's quite possible that there is some way to do "a", however I did ask > support and they claimed there to be no way. > > thanks for the advice anyway. > regards > allan >
Is your .bash_profile or .profile being executed? Is BASH_ENV set? Is support saying that, as a matter of policy, no per-user environment customisation is allowed for non-login non-interactive shell invocations? -- Peter B. West <http://cv.pbw.id.au/> Folio <http://defoe.sourceforge.net/folio/> _______________________________________________ darcs-devel mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-devel
