Michael Sinz wrote:
> On 12/1/05, Max Bowsher <maxb1@ukf.net> wrote:
>
>>Michael Sinz wrote:
>
> [...]
>
>>>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
I misread the suggestion and took it to mean that the file to reference
is stored *in* a subversion repository. The follow up post saying "where
would that live" made me realise I misunderstood, but also the idea of
the control file living in the repository struck me as kinda cool, e.g.
obey the head revision of this path, where path can be a repository URL
(though a remote URL would be daft).
Then another thought crossed my tired brain: PostgreSQL has database
tables representing its' state and I'm sure there's an example I can't
quite bring to mind of a system storing its' settings in itself... made
me think of a repository server having a special repository which is
used to store its config with the benefit of versioning changes to the
config.
Call me crazy, just thought it was interesting. Not thought through,
probably lots of holes in the idea. Apologies for hijacking the thread,
please start a new thread if there are replies to this.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 2 00:17:02 2005