Re: Syntax for templated SVNPath
From: Thomas ┼kesson <thomas_at_akesson.cc>
Date: Wed, 14 Aug 2013 01:41:19 +0200
On 9 aug 2013, at 17:52, C. Michael Pilato <cmpilato_at_collab.net> wrote:
> Put simply, CollabNet wants to start using dynamic virtual hosting with
First of all, I like this enhancement, a lot.
> There are obviously many configuration settings which are common across
To make this enhancement complete, I believe all settings that take a "directory-path" should be handled identically (allow the templating). To me, the most obvious example is "AuthzSVNAccessFile". It wouldn't make sense to separate repositories for different vhosts but keep a single huge access file.
I like the choice of syntax, makes sense in httpd config and it's expandable, see related issue below.
> But along the way, our conversation led us to the problem of option
Agree, duplicating the directives is not the way to go. But deprecating SVNParentPath seems a bit over the top. SVNPath vs SVNParentPath are 2 quite distinct modes of operation and many many configs use them so I get the feeling SVNParentPath can't be removed for a long time anyway.
I propose either of:
1. SVNPathTemplates on | off
Where the option applies to all SVN* options that take a pathspec, including the authz options.
> The discussion you are now privy to is all about how we can make our
I would like to throw in a related issue that I was thinking about while studying the release notes of svn 1.8. We (Simonsoft) are _very_ exited about the "In repository authz". In our setups, the access file (currently one per server) is managed in a separate repository, but we have to manually ensure the latest one is on disk (svn up). All our servers have an "admin" repo containing server config including the access file.
We would like to transition to:
However, there is a problem with referencing separate access files that way when using SVNParentPath. We would need the same templating concept:
This is somewhat out of scope for this discussion, but still a validation that the templating syntax can also address this limitation.
This is an archived mail posted to the Subversion Dev mailing list.