Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<03fe01c4f354$c06a4950$5308a8c0@robinson.cam.ac.uk>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	<cygwin AT cygwin DOT com>
References:	<E1CmDbo-000O9m-Pe AT mk-mx-2 DOT b2b DOT uk DOT tiscali DOT com> <03b101c4f352$db573590$5308a8c0 AT robinson DOT cam DOT ac DOT uk> <Pine DOT GSO DOT 4 DOT 61 DOT 0501051321140 DOT 7503 AT slinky DOT cs DOT nyu DOT edu>
Subject:	Re: Problems with subversion svn+ssh
Date:	Wed, 5 Jan 2005 18:31:01 -0000
MIME-Version:	1.0
X-IsSubscribed:	yes

Igor Pechtchanski wrote:
> Would adding a /etc/profile.d/subversion.sh with
>
> export PATH="/usr/lib/subversion/bin:$PATH"
>
> be a good solution, or was the whole point to not have the executables in
> the PATH?

Already exists!

But for an ssh single command, no login shell is ever executed, so profile 
is not run.

The only other place to hook in to the ssh login process is /etc/ssh/sshrc, 
and I don't think that amount of complexity is worthwhile.

I'm inclined to just revert the whole /usr/lib/subversion/bin thing, and 
just put up with the fact that it then won't be possible to use perl/python 
subversion bindings linked against a self-built subversion whilst the 
subversion package is installed.

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -