svn+ssh: specifying full path to svnserve

[Robert Guthrie <rg...@pobox.com>]

Is there a way, either in the config files or by modifying the source, 
to make the svn+ssh protocol to use the full path to the svnserve protocol?

I've looked at .subversion/config, but the tunnel options only seem to 
be able to modify the command for the tunneling program, not what 
command is invoked for svnserve.

Thanks

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn+ssh: specifying full path to svnserve

[Eric Hanchrow <of...@blarg.net>]

You might just write a wrapper program, named svnserve, that is on
your path.
-- 
Tobacco: It's not just for killing children anymore.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn+ssh: specifying full path to svnserve

[Robert Guthrie <rg...@pobox.com>]

Roger Keays wrote:
> Hi Robert,
> 
> 
>>Is there a way, either in the config files or by modifying the source,
>>to make the svn+ssh protocol to use the full path to the svnserve protocol?
> 
> 
> What do you mean by 'the full path to the svnserve protocol' ?

I don't know what that means, but I can tell you what I wanted to ask...

Is there a way to specify the full path to svnserve when connecting to a 
remote repository via svn+ssh?  I have svnserve in a non-standard 
location on machine A, and from machine B, all I have for conneting to 
the repository is the ssh protocol.  When I am on B, and try to do an 
svn list svn+ssh://A/repository/location/ , it reports that it can't 
find the svnserve executable on machine A.


>>I've looked at .subversion/config, but the tunnel options only seem to
>>be able to modify the command for the tunneling program, not what
>>command is invoked for svnserve.
> 
> 
> I had what sounds to be a similar problem - i.e. I wanted to use abbreviated
> paths for the svn+ssh protocol, but since svnserve is always invoked by the ssh
> daemon on the server I had difficulty passing the -r parameter.
> 
> My solution was to replace the svnserve binary with a script (and rename the
> binary):
> 
> #!/bin/sh
> /usr/bin/svnserve-real -tr/var/local/svn/
> 
> Hope this helps, and also interested to know if there is a better way to do
> this.

This looks like the best solution I could come up with for your dilemma, 
but my problem is not related.  From a remote machine, I can't find the 
svnserve executable in the limited PATH set when tunneling via ssh.

Thanks for your input though, and I hope my explanation is clearer this 
time.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org