On Wed, Jan 26, 2005 at 10:39:10AM -0500, David Coppit wrote:
> In the subversion book it's recommended that you use a wrapper to make
> sure that permissions are not hosed by a user with a restrictive umask:
> 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,
> 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? If so, is there a fix like the above that doesn't require
> diverging from the default installation?
You can ask all users to put 'umask 002' into their .bashrc files (or,
if the users do not have full shell accounts, ask the admins to set the
umasks for those users to 002).
It works for me: http://mg.pov.lt/blog/setting-umask-for-subversion.html
Computers are not intelligent. They only think they are.
Received on Wed Jan 26 23:16:26 2005