On 02.08.2014 15:20, Alan Barrett wrote:
> On Tue, 29 Jul 2014, C. Michael Pilato wrote:
>> This leaves open the possibility of a future additional match mode for
>> regular expressions (using the '^:' magic prefix) should we seek to "go
>> there".
>>
>> # Match the trunk and branches subdirs and their children.
>> [repos:^:^/(trunk|branches)(/.*|$)$]
>
> As a user, I'd prefer to see keywords rather than unusual characters
> to designate special syntax. For example, I would prefer
> [glob:/tags/*/private] and [regex:/tags/.*/private] to
> [*:/tags/*/private] and [^:/tags/.*/private].
Quite understood. Unfortunately, the syntax you propose above cannot
work; [thing:/path] is already a valid syntax, and if we did what you
propose, we'd no longer be able to create rules for repositories named
"glob" and "regex". Worse, this could change the meaning of existing
authz files.
We could do something like this, though:
[:glob:/path]
[:glob:repos:/path]
In the old authz files, these rules would be invalid, because the
repository name part (the substring up to the first colon) cannot be empty.
Thoughts?
-- Brane
--
Branko Čibej | Director of Subversion
WANdisco | Realising the impossibilities of Big Data
e. br...@wandisco.com
