On 2/15/07, Kylo Ginsberg <kylo.ginsberg@gmail.com> wrote:
> I'm converting a cvs repos to svn which includes an access-restricted
> directory. Two questions about the path-based access control:
>
> 1) Are wildcards supported in the path specification? or can I
> otherwise avoid adding an entry to the access-control file every time
> the directory is branched?
Unfortunately, no.
> 2) The svnbook refers to performance implications, stating ominously:
> "in certain situations, there's very noticeable performance loss".
> Can anyone elaborate? Is this specific to http vs svn access? does it
> linearly track # of paths specified? what ops, etc?
I think it's both http and svn access.
> Any guidance appreciated. As an alternative to the path-based access
> control, I have the option of segregating the access-restricted
> directory to a separate repository but that carries its own baggage.
Another option for you might be svnperms.py. You install it as a hook
script and it can give you much more flexibility in your access
controls. Haven't used it myself, but it may fix your wildcard
problem, and may be better in terms of performance as well.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 15 19:06:07 2007