commit-access-control vs. AuthzSVNAccessFile

Dear all,

fiddling around with subversion, appreciating subversion more
everyday, I stumbled over AuthzSVNAccessFile in the subversion book.

It has risen the following questions in mind:

- AuthzSVNAccessFile sections:
  Am I right that the sections support perl-regex as well?
  i.e.:

    [repos:/[a-e]]
    * =

    [repos:/[f-i]]
    * = r

    [repos:/[j-z]]
    * = rw

  would deny access completely to the projects a to e, allow read
  access to all projects f to i, and read-write access to the projects
  j to z.

- Is there any fundamental difference from a user perspective between
  AuthzSVNAccessFile and commit-access-control except that
  AuthzSVNAccessFile is more powerful by that it allows also to deny
  access to a project completely?

- Am I right that I do not need to restart apache2 every time I
  modified anything in an access control file of AuthzSVNAccessFile?

- Parent directories must be accessible if a directory must be
  accessed?
  i.e.:
    [repos:/[a-e]]
    * = r

    [repos:/[a-e]/input]
    * = rw

    would work

  while

    [repos:/[a-e]]
    * =

    [repos:/[a-e]/input]
    * = rw

    wouldn't?

Thanks for any clarification!

wbr,
Lukas

-- 
Lukas Ruf           | Wanna know anything about raw |
<http://www.lpr.ch> | IP? -> <http://www.rawip.org> |
eMail Style Guide: <http://www.rawip.org/style.html>|
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org