On 11/8/05, Stephen Gross <sgross@darwin.epbi.cwru.edu> wrote:
> Ok, so I've got my script running svnperms... sort of. I haven't set up a
> svnperms.conf file yet (which I need to do). Two questions, first:
>
> (1) When I do a svn commit, the error reads "can't read config file
> /home/repos/svn/sage/conf/svperms.conf". Shouldn't it read "can't read
> config file /home/repos/svn/sage/hooks/svnperms.conf" ? Why is it looking in
> a 'conf' directory?
>
-f PATH Use PATH as configuration file (default is repository
path + /conf/svnperms.conf)
> (2) I still haven't found actual *reference* information for the
> configuration file. Does this information exist anywhere? If it doesn't,
> here's the permissions I want to set up:
>
> for the admin user: read/write on everything
> for everyone else: read/write on /branches, read on /trunk.
>
Adapted from example 3
from http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/svnperms.conf.example
#
# Another common structure, expecting a project name inside the repository
# (like trunk/myproject/ and tags/myproject/). In this example, only admins
# are allowed to create projects, and there are project specific access
# lists.
#
[example3 groups]
admins = john
[example3]
trunk/[^/]+/ = @admins(add,remove,update)
branches/[^/]+/ =*(add,remove,update)
Can't garuntee this works, but the conf.examples file and the help
from the script itself is all that's there documentation wise.
Josh
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 9 16:37:32 2005