Re: avoiding umask headaches
Andrew McNabb wrote:
> 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?
Creating an /etc/svnserve.conf has been considered, and is likely to
happen eventually - I believe it's mainly an issue of "when someone gets
around to writing the code".
Received on Tue Nov 7 22:43:02 2006
This is an archived mail posted to the Subversion Dev