Yes, thats what I found.
But <Location xxx> requires a full path and I can deny the rights
for /trunk/commonprojects/myproj. But if I make a branch to
/branches/version_1_4/commonprojects/myproj I have to create new
permissions for this branch.
So I want to protect only the directory myproj regardless of the
position in the repository layout, eg if it was tagged, branched
or copied.
I can try <LocationMatch .*/myproj/.*>, but don't know if this
works and how slow it is. Additional I do not protect the file or
directory, but a regular expression within a filename.
Another disadvantage of the apache-api is that I have to use apache.
The suggested approach to define a layout like /myproj/trunk and
/myproj/branches works with <Location xxx> but due to the dependencies
between our different projects we cannot use it. If we create a branch,
we have to branch all projects together.
Also the rights can't be set from a user, only from the server administrator.
jan
> -----Original Message-----
> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: Monday, August 30, 2004 4:30 PM
> To: Jan Mönnich
> Cc: svn-dev-list
> Subject: Re: Idea for a more sophisticated user rights management
>
>
> On Mon, 2004-08-30 at 06:32, Jan Mönnich wrote:
> > Hello,
> >
> > with apache and webdav a litte user management can be used.
> But the problem is that only
> > the main directories may be protected. If I have all
> projects below the branches directories
> > (eg /trunk/proj1 /trunk/proj2 /branches/version1/proj1) its
> not possible to set up
> > some user rights. So I can protect /trunk/proj1 but not
> /branches/ver20/proj1 automatically.
>
> This is why we have mod_authz_svn. Please look at chapter 6.
>
>
Received on Mon Aug 30 16:56:02 2004