Issue setting up authz permissions

[Robert Kinberg <rk...@hotmail.com>]

I am having trouble setting up authz directory level permissions (in a 
manageable way). I have the standard /branches, /tags, /trunk directory 
structure. I have a directory named /trunk/secret that I want to restrict 
access to. I can setup authz to do this fine:

[/trunk/secret]
@secretusers = rw
* =

That works great. However, once I branch or tag the /trunk directory, the 
permissions no longer apply to the new branch/tags. Is there anyway to setup 
relative authz permissions, like ./secret, perhaps. Otherwise, everytime I 
branch/tag the /trunk, I will need to create another authz entry to protect 
the new instance of the secret directory.

Any thoughts?

Robert



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Issue setting up authz permissions

["Kevin P. Fleming" <kp...@digium.com>]

Robert Kinberg wrote:

> That works great. However, once I branch or tag the /trunk directory, 
> the permissions no longer apply to the new branch/tags. Is there anyway 
> to setup relative authz permissions, like ./secret, perhaps. Otherwise, 
> everytime I branch/tag the /trunk, I will need to create another authz 
> entry to protect the new instance of the secret directory.

Unfortunately that is not possible with the current mod_authz_svn 
implementation.

I can suggest an alternative; put your secret stuff under /secret/trunk, 
  /secret/branches, /secret/tags, and put a 'secret' svn:externals 
property into /trunk. This will provide most of what you are looking 
for, almost transparently.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org