On Tue, Sep 19, 2006 at 11:08:28AM +0200, Stefan Petri wrote:
> Hi!
>
> I have stumbled across several cases where access via tunneling failed
> because the remote svnserve binary was not in a system default search
> path. The subversion FAQ and manual show the workaround via tweaking ssh
> key configuration, but I have several cases where that is not
> applicable. So, here is 4-line patch , which takes the command to invoke
> from the environment variable SVN_REMCMD. If that is not set, the remote
> command defaults to "svnserve".
> Enjoy,
> Stefan
>
> [[[
> subversion/libsvn_ra_svn/client.c use SVN_REMCMD to override hardcoded
> "svnserve"
>
> To circumvent problems with the hardcoded invocation of "svnserve" on
> the remote end of tunnels, look for environment variable SVN_REMCMD.
> Fall back to "svnserve" if that is not set.
> This helps when e.g. the svnserve command is not in the remote systems
> default search path, and ssh key trickery as descibed in the Subversion
> manual is not applicable.
> ]]]
>
Why not make SVN_SSH point to a shell script that replaces the "svnserve"
parameter with something else?
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 1 04:35:07 2006