Why do you need one working copy?
> On Sep 7, 2015, at 5:31 AM, Holger Schmidt <Holger.Schmidt_at_zmdi.com> wrote:
>
> Hi,
>
> There is a repository with this directory tree:
>
> root
> +- dir_a
> +- dir_b
> | +- dir_c
> | +- dir_d
> +- dir_e
> +- dir_f
> +- dir_g
>
> Because there is sensible data in there user usr_u has read/write access only to dir_c and dir_g.
>
> Question: How do I configure this with the path based authorization (Apache + mod_authz_svn + AuthzSVNAccessFile) and with one working copy?
>
> For one working copy usr_u needs to checkout the root directory. That means he needs read access for the root, dir_b, and dir_e. Without read access SVN denies to checkout something (initial checkout or update within sparse working copy). So I have to remove access for dir_a, dir_d, dir_f. That makes six directory sections:
>
> [/]
> usr_u = r
> [/dir_a]
> usr_u =
> [/dir_b/dir_c]
> usr_u = rw
> [/dir_b/dir_d]
> usr_u =
> [/dir_e/dir_f]
> usr_u =
> [/dir_e/dir_g]
> usr_u = rw
>
> I constantly need to monitor the repository to remove the read right for newly created directories.
>
> Is there a way to configure it like this:
>
> [/]
> usr_u =
> [/dir_b/dir_c]
> usr_u = rw
> [/dir_e/dir_g]
> usr_u = rw
>
> Please Cc me in any responses as I'm not subscribed to this list.
>
> Thanks,
> Holger
>
Received on 2015-09-07 16:20:16 CEST