My user base isn't exactly made up of power users... they already balked a little when I showed them how to configure tortoise and putty. I can only imagine handing them more customization.
I think I'll try the symlink option, but set it up with automount thanks, Matt ---------------------------------------- Matthew Beals Michigan Technological University Department of Atmospheric Sciences 1400 Townsend Drive B019a Fisher Hall Houghton, MI 49931 mjbe...@mtu.edu ----- Original Message ----- From: "Daniel Shahaf" <d...@daniel.shahaf.name> To: "beals...@gmail.com" <mjbe...@mtu.edu> Cc: "svn" <users@subversion.apache.org> Sent: Saturday, September 10, 2011 8:42:13 AM GMT -05:00 US/Canada Eastern Subject: Re: customizing svnserve for svn+ssh Stefan Sperling wrote on Sat, Sep 10, 2011 at 14:37:58 +0200: > On Sat, Sep 10, 2011 at 08:24:24AM -0400, beals...@gmail.com wrote: > > Sorry, I should have been more verbose with the description of my shell > > script. > > > > So am I to take it that intercepting and altering the path isn't possible > > in a simple wrapper script? > > One way of shortening the repository path in an svn+ssh URL is placing > symlinks into the root filesystem of the svn server. > > You could create symlinks like this: > > /Code -> /repos/Code > /<username> -> /home/<username>/.repos Another option is to have the client issue a different command depending on which of the two it wants. That does involve client-side setup --- either in ~/.subversion/config[tunnels] or in ~/.ssh/config[Host, IdentityFile, ...].
