Re: permissions wrapper and svn+ssh?

On 2005.01.26 10:39:10 +0000, David Coppit wrote:
> My sysadmins don't want to diverge from the default installation, so I
> plan to create this wrapper as /home/coppit/bin/svn in my own account,
> and
> tell the developers to add /home/coppit/bin to their PATH before
> /usr/bin.(They trust me not to put a nefarious ls in there. :)
>
> My question is this: Do I need to worry about permissions with svn+ssh
> access?

Yes.

> If so, is there a fix like the above that doesn't require
> diverging from the default installation?

If you have to use svn+ssh, have to use /usr/bin/svn, and your sysadmins
won't help, then I think your workaround is just about optimal. Sorry.

If svn isn't already installed on the system, and you're allowed to
compile software, then one minor improvement would be putting the whole
thing off your $HOME, then renaming svn to svn.donotrun. That way
a user who forgets to put your $HOME/bin in his PATH will get "command
not found" instead of messing up the repository.

-- 
David Ripton    dripton@ripton.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org