[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Repository permissions, q.v. $CVSUMASK

From: Colin Watson <cjwatson_at_flatline.org.uk>
Date: 2003-02-04 03:56:26 CET

I'd like to set up my Subversion repository so that it can be accessed
using any of ra_dav, ra_local, or ra_svn, each by multiple users. Since
ra_dav runs as the Apache user, and ra_local and ra_svn run as whatever
user's doing the accessing, this means that I need to have a
group-writable repository.

Now, Subversion appears to honour the prevailing umask, so I can set
'umask 002' and everything will work. However, I need to do this for
Apache as well, which is a little more awkward and I'm not sure if it
has any ramifications. Plus I have to get every user to do the same,
since otherwise a commit that happens to cause the filesystem to create
a new log file will create it such that nobody else can write to it. On
a system not enlightened enough :-) to use a one-group-per-user setup,
'umask 002' isn't something users will want to do lightly either.

CVS handles this reasonably well: it defaults to umask 002, which can be
overridden if needed using CVSUMASK. It's not ideal (although I don't
know very much about CVS internals), but it usually works well enough in
practice. Could Subversion include at least something like that, or
maybe more flexible, in order to bring RA layers other than DAV up to
the level of CVS for group projects? If so, I'd be happy to try to help,
given some pointers as to where to start.

(I've read the "Permissions, Authentication, and Authorization" section
of the Book. However, if I've missed something, I apologize.)


Colin Watson                                  [cjwatson@flatline.org.uk]
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 4 03:57:11 2003

This is an archived mail posted to the Subversion Dev mailing list.