[PATCH] Document svnserve/mod_dav_svn inconsistency

[C. Michael Pilato]

We try to avoid runs of multiple admonishments in the book.  I'm going to
take your suggested text (which is good) and use it when reworking this
portion of the section.

On 02/27/2012 10:04 AM, Daniel Shahaf wrote:
> [[[
> Follow-up to r1294134:
>
> * en/book/ch06-server-configuration.xml
>   (svn.serverconfig.pathbasedauthz):
>     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>
>  
> +    <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>
> ]]]
>
> _______________________________________________
> svnbook-dev mailing list
> svnbook-dev at red-bean.com
> http://www.red-bean.com/mailman/listinfo/svnbook-dev