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

svnperms.conf Help

From: Rob Wilkerson <r.d.wilkerson_at_gmail.com>
Date: 2007-07-17 02:44:17 CEST

I have a new repository set up that will house any number of projects:


I have several teams and would like to limit commit access to each
project based on the working team. svnperms.py is being executed in
my pre-commit hook, but I have very little (read: none) experience
with svnperms.conf so I'd like a sanity check from anyone with more

@admin can create new project structures and add, remove, update any
part of any project
@team can add, update, remove project/branches
@team can add, update, remove project/trunk

Pretty simple, I think. For better or worse, my svnperms.conf looks like this:

admin = user1 user2
team1 = user3 user4 user5 user6
team2 = user7 user8 user9 user10
team3 = user11 user12 user5

.* = @admin(add,remove,update)

branches/.* = @team1(add,remove,update)
trunk/.* = @team1(add,remove,update)

branches/.* = @team2(add,remove,update)
trunk/.* = @team2(add,remove,update)

I'm afraid that I don't have a good feel for whether I'm identifying
the projects properly (using square brackets) or whether I've applied
the global admin permissions properly. Although there are a number of
sample svnperms.conf files out there, none seem to explain the syntax
very well (at least not well enough for me to feel comfortable that
I've got it correct).

Any suggestions, insight or corrections would be much appreciated.

Thank you.

Rob Wilkerson

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 17 02:43:40 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.