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

Re: Square brackets in file names and authz (in VisualSVN 2.5.5)

From: Thorsten Schöning <tschoening_at_am-soft.de>
Date: Thu, 12 Jul 2012 12:53:36 +0200

Guten Tag Jason Heeris,
am Donnerstag, 12. Juli 2012 um 11:51 schrieben Sie:

> I don't really know *what* constraints there are on honouring existing
> authz file syntax, whether or not it's explicitly specified.

How about just telling svn explicitly which parse mode for section
names one wants? If the current problem is that file name characters
interfere with authz configuration syntax and backwards compatibility
may become a problem because of relatively easy/weak rules for section
names before, just create a new, better defined and documented rule.
This rule may be that everything between the first [ and the last ] is
used as section name and because it's a new rule every new user would
prevent adding some sorts of comments in the same line as the section
name or one would add them according to the new rule. Comments on the
same line as the section names won't occur on complex section names,
though, because complex section names will force complex comments, if
any.

From my point of view the only problem is to find something which tells
svn about the new parse mode and when I look at parse_section_name I
would just choose something which is not allowed as a repository name
in the context where authz could be used and add that to a section
name to indicate a new rule. This way old syntax and behaviour won't
break, one could fit each path's needs to whatever processing rule
may be added in the future and everything can be handled directly in
parse_section_name without even breaking internal interfaces. I would
just try to add something like a version number, like in the following
examples.

configured: [repo:/path/to/[12345] file.ext] # Comment comment [comment]
rule version: 1
section name: repo:/path/to/[12345]

configured: [^2^repo:/path/to/[12345] file.ext] # Comment comment [comment]
rule version: 2
section name: repo:/path/to/[12345] file.ext] # Comment comment [comment

But on a second look, seems a bit ugly... :-/

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow
Received on 2012-07-12 12:54:16 CEST

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

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