avoiding umask headaches

Back in 2003, someone posted "RFC: svnserve.conf umask directive". As
far as I can tell, nothing has happened with this yet. I was just
curious what the current plans are for fixing Subversion with svn+ssh
and file so it works with groups.

Most people seem to be recommending:

1) Get root access on the machine you are using.

2) Move /usr/bin/svn and /usr/bin/svnserve to /usr/bin/svn.orig and
/usr/bin/svnserve.orig (thus breaking upgradability if you are using a
package manager)

3) Create /usr/bin/svn and /usr/bin/svnserve wrapper scripts, which
assumes that all users on the system always want to create
group-writable repositories

As it is, we have students on a shared system who would like to use
version control for group projects, but I can't recommend Subversion to
them because they cannot set up a system-wide wrapper script. Is there
any other possible solution to the problem? Are there any plans to fix
the problem permanently, preferably with a config file somewhere?

Thanks.

-- 
Andrew McNabb
http://www.mcnabbs.org/andrew/
PGP Fingerprint: 8A17 B57C 6879 1863 DE55  8012 AB4D 6098 8826 6868
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org