Proposed enhancement: umask directive in svn/svnserve configuration

Hi all.

I'm maintaining a private repository with multiple access methods
(particularly: svn+ssh:/// and file:///)

I'm experiencing problems related to file permissions. I've created
wrappers for svn, svnserve, svnlook and svnadmin in /usr/local/bin this
way:

#!/bin/sh
umask 002
/usr/bin/svnserve "$@"

/usr/local/bin is before /usr/bin in $PATH, and the "db" directory in
each repository has setgid bit activated, so files created in that
directory should be created with appropiate owner and permissions.

The problem is that, sometimes, when I or any other of my colleagues
commit changes made to the repository, he gets an error. If I check the
repository db files, I can see that there's a new file with correct
owner/group (owner = the user who committed the last change, group = the
group that owns the db directory), but with incorrect permissions
(rw-r--r-- instead of rw-rw-r--).

I must launch svnadmin recover and chmod the new file manually for it to
work.

Perhaps the problem is that svnserve is launched directly, and not
through the wrapper... It seems it's not the problem, because the
wrapper write some log messages into files, and this messages are
actually written when committing changes.

My system is Debian, and I wouldn't like to maintain a self-compiled
version of the software installed, for example, in /usr/local/subversion
(as in the Tutorial example).

I think it would good if subversion had a configuration option for
choosing the umask used when accessing/modifying the repository running
svnserve or svn. This way, making wrappers would not be more neccessary.

What do you think about this possible feature?

-- 
David Marín Carreño <dmarin@dyr.es>
Desarrollo y Recursos, S.L.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org