Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <03fe01c4f354$c06a4950$5308a8c0@robinson.cam.ac.uk> From: "Max Bowsher" To: References: <03b101c4f352$db573590$5308a8c0@robinson.cam.ac.uk> Subject: Re: Problems with subversion svn+ssh Date: Wed, 5 Jan 2005 18:31:01 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit 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/