> -----Original Message-----
> From: Hoping White [mailto:baihaoping_at_gmail.com]
> Sent: Wednesday, November 24, 2010 9:22 PM
> To: users_at_subversion.apache.org
> Subject: Db based configuration for per-directory access control
> Hi all
> Is there any way to configure subversion to do per-directory access
> control via database not config file? I have googled a lot, and all
> found are telling how to configure apache login problem, not svn
> repository access control.
Not that I know of. As a result, I'm currently using Apache to manage
per-directory access control to SVN repositories and IMO it is a hassle
using the Apache mechanism. The main limitation for me is during branch/tag
creation. Since there are no automated tools to duplicate permissions based
on the trunk permissions an admin must manually edit the AuthzSVNAccessFile
and copy/edit trunk permissions manually whenever a branch or tag is
created. As a result of the manual method, it is very easy to leave
permission holes open when branches/tags are created without admin knowledge
or when new permissions are added to the trunk and the admin forgets to
manually propagate the change to all branches/tag directories.
I personally would prefer an SVN-based, not Apache-based, access control
method and SVN-provided automation tools to automatically duplicate
permissions during branch/tag creation. FWIW, I imagine adding automation
would be easier for the SVN dev team if permissions were stored directly in
SVN repositories rather than in Apache's text-based AuthzSVNAccessFile.
However, they would have to duplicate some of the logic already existing in
Apache (n.b. a small price, IMO). Regardless, I do not know if these admin
issues are on the SVN dev team's radar, but I will search later and file an
enhancement request if I can't locate an existing request.
Received on 2010-11-29 20:15:07 CET