-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Sinz wrote:
> On 12/1/05, Max Bowsher <maxb1@ukf.net> wrote:
>
>>>I too would like to add a measure of support/request for such a feature.
>>>It would make supporting large numbers of repositories with various
>>>administrative controls much more scalable.
>>
>>I think it's a reasonable request.
>>
>>However, it cannot be done simply with a relative path in the
>>AuthzSVNAccessFile directive, because this already has a meaning: it
>>looks for the authzfile relative to Apache's ServerRoot - which is kind
>>of expected behaviour, since other directives such as Include or
>>AuthUserFile so the same thing.
>
>
> That is understandable. I would think it would need to be a
> different option and that then this file would be part of the
> repository tree (beside the hooks directory or in the conf
> directory?)
>
> That way it would be the "authz" file in each repository.
>
> The option would be something like:
>
> AuthzSVNPerRepository On
This has the disadvantage that the directive meaning is changed by
another, potentially appearing many lines distant.
I'd suggest instead:
AuthzSVNAccessFileInRepository my-authz-file
Max.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
iD8DBQFDj1bQfFNSmcDyxYARAgD6AKCBcM3d6eIzMpXnsoogL5eG43RtbgCfRrDM
EFWIB0s6nIS5BLYogZ4ytK4=
=KeAx
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 1 21:16:54 2005