On 7/27/07, Andy Levy <andy.levy@gmail.com> wrote:
> On 7/27/07, Johnathan Gifford <jgifford@wernervas.com> wrote:
> > I've looked at the Subversion booked and searched the Internet for
> > solution to this with no luck.
> >
> > I have a repository with a group that only has write privileges on
> > branches for all known paths in the repository. However, if a new
> > project is created in the repository with a set of tags, trunks, and
> > branches under it, this group cannot write to that directory until I add
> > the new project branch path to the authorization file. Being the
> > administrator that doesn't like to have to do everything all the time
> > for the users, my question is: Does the mod_authz_svn support
> > authorization files with regex patterns or wildcards for repository
> > paths?
> >
> > Basically this might look like:
> >
> > [therepo:/]
> > @thatgroup = rw
> > @thisgroup = r
> >
> > [therepo:*/branches]
> > @thisgroup = rw
> >
> > The purpose of this is to keep the team that uses that repository from
> > always coming back to me so the new projects don't have to be added to
> > the authorization file each time. If Subversion doesn't support this
> > kind of syntax with mod_authz_svn, do you think a feature request should
> > be made to do so?
>
> Wildcards aren't supported. There may already be a request in the
> Subversion bug database, have you searched it yet?
>
> You could also look at svnperms.py.
There's a patch somewhere in the dev@ mailing list archives to add
wildcards. There were a lot of remarks making it impossible to add in
the state it was in, but it was functional. You may want to have a
look.
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 27 17:21:49 2007