Re: Multiple access filess when using SVNParentPath
On 11/29/05, Carlos Alberto Costa Beppler <firstname.lastname@example.org> wrote:
> Because different people will have access to modify the policy and I
> can not give them rights to modify only parts of the file.
In my company I use Apache module mod_macro and repository
configuration take one line (Use SvnRepos test-repo). Also I place
configuration for each repos in separate file to easy detaching for
> On 11/28/05, Ben Collins-Sussman <email@example.com> wrote:
> > On 11/28/05, Carlos Alberto Costa Beppler <firstname.lastname@example.org> wrote:
> > > +1 for a new feature where I can specify that the AuthzSVNAccessFile
> > > is a relative path to the repository repository location (using the
> > > conf directory as base by example).
> > >
> > > This can be very useful when using SVNParentPath and delegating the
> > > administration of the access control.
> > >
> > > To not break the compability with existing configuration this could be
> > > enabled by adding a new command to mod_authz_svn like
> > > "AuthzSVNRelativePath" or something like this.
> > >
> > I don't understand, why do you want separate authz-policy files for
> > separate repositories, when you can already control access to *all* of
> > them with a single policy file?
Received on Tue Nov 29 09:07:42 2005
This is an archived mail posted to the Subversion Dev