[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Patch] Expression support for SVNPath and SVNParentPath

From: Graham Leggett <minfrin_at_sharp.fm>
Date: Fri, 27 Feb 2015 02:14:21 +0200

On 26 Feb 2015, at 10:18 PM, Mark Phippard <markphip_at_gmail.com> wrote:

> Just a note to those reviewing this patch. C-Mike did something "similar" on a branch here:
> http://svn.apache.org/repos/asf/subversion/branches/SVNParentPathTemplate/ <http://svn.apache.org/repos/asf/subversion/branches/SVNParentPathTemplate/>
> I notice there is no branch.readme but the commit messages probably explain the behavior and there was thread on it here:
> http://svn.haxx.se/dev/archive-2013-08/0168.shtml <http://svn.haxx.se/dev/archive-2013-08/0168.shtml>

By way of background, I added the regex named grouping support to httpd that allowed you to do stuff like <LocationMatch ^/svn/(?<CUSTOMERNAME>[^/]+)/>, and I’ve been adding expression support to a growing list of httpd directives, starting with all the require directives, and then following up with Alias and Redirect.

What I’m trying to achieve is to lower the cost of httpd directives, both in terms of the amount of config required to achieve a certain aim, as well as making it possible to administer an httpd server (and svn repository) using changes to an LDAP directory only.

I chose the two argument layout for SVNPath and SVNParentPath as it was both backwards compatible with existing configs and had the side effect that the expression could be rooted below a specific root directory for safety, given that the directory pointed at by SVNPath isn’t protected (to my knowledge) by <Directory> blocks. It also had the side effect that SVNParentPath could give us a list of repositories rather nicely.


Received on 2015-02-27 01:14:52 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.