On Mon, 2004-08-30 at 09:55, Jan Mönnich wrote:
> 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.
Yes, this is exactly why, in the long term, we'd like to implement ACLs
directly in the repository itself. Your suggestion isn't a new one.
:-) That way, permissions can be directly attached to versioned
objects. For now, all you can do is path-based access control.
I don't understand, however, why you're talking constantly about
<Location> directives. It's far easier to do path-based access control
using mod_authz_svn's accessfile format, rather than trying to control
paths from within httpd.conf. Here's the relevant section of the book:
http://svnbook.red-bean.com/svnbook/ch06s04.html#svn-ch-6-sect-4.4.2
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 30 17:00:49 2004