[PATCH] Document svnserve/mod_dav_svn inconsistency

Daniel Shahaf danielsh at elego.de
Mon Feb 27 09:04:58 CST 2012

Follow-up to r1294134:

* en/book/ch06-server-configuration.xml
    Document the difference in expectations of REPOS_NAME in authz rules
    between mod_dav_svn and svnserve.

Index: ch06-server-configuration.xml
--- ch06-server-configuration.xml	(revision 4252)
+++ ch06-server-configuration.xml	(working copy)
@@ -3448,10 +3448,26 @@ sally = r
         example—when providing directory listings of repository
         content.  Be aware, however, that when consulting the access
         file for authorization rules, Subversion uses this repository
-        basename for comparison, <emphasis>not</emphasis> any
+        pathname for comparison, <emphasis>not</emphasis> any
         configured human-friendly name.</para>
+    <warning>
+      <para>What pathname is used to specify the repository depends on the
+        server configuration: <command>mod_dav_svn</command> uses the
+        repository directory's basename, while <command>svnserve</command>
+        uses the relative path from the serving root (as determined by its
+        <option>--root</option> (<option>-r</option>) command-line option) to
+        the repository.</para>
+      <para>Care should be taken, therefore, when a repository is served by
+        multiple servers, to ensure that the section names are compatible with
+        the different server's idea of what the repository name should
+        be—for example, by configuring <command>svnserve</command>'s
+        root to be the same as the <literal>SVNParentPath</literal>, by
+        avoiding embedding repository names in section names.</para>
+    </warning>
     <para>Of course, permissions are inherited from parent to child
       directory.  That means we can specify a subdirectory with a
       different access policy for Sally:</para>

More information about the svnbook-dev mailing list