[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Issue setting up authz permissions

From: Robert Kinberg <kinberg_at_tecore.com>
Date: 2006-02-06 14:24:36 CET

I tried the svn:externals approach also. This seems like it may work.
However, svn:externals are not copied when an svn copy is made? I use
TortoiseSVN and it seems like the svn:externals properties are not
preserved thru the copy.

Any thoughts?


-----Original Message-----
From: Kevin P. Fleming [mailto:kpfleming@digium.com]
Sent: Sunday, February 05, 2006 9:59 PM
Cc: users@subversion.tigris.org
Subject: Re: Issue setting up authz permissions

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

Unfortunately that is not possible with the current mod_authz_svn

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
Received on Mon Feb 6 14:27:35 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.