Guten Tag Branko Čibej, am Samstag, 21. September 2019 um 19:53 schrieben Sie:
> Basically it's as likely as someone contributing a patch for that. Note > that this may not be trivial due to backwards-compatibility concerns, > not only about how repositories are found on disk but also (as Daniel > mentioned) how their names are used in path-based authz rules. Thanks Daniel and Branko for clarifying this, saves me from retesting things. :-) Sadly I'm not able to provide a patch, so would only like to mention that the problem regarding authz-files is worked around by "AuthzSVNReposRelativeAccessFile" in my setup. This way I simply don't have repo names in that file and if a new feature like "SVNRoot" is designed anyway, this might make things easier to start with. > <Location "/svn/Src/DocBeam/Clients"> > DAV svn > SVNParentPath > "/home/ams_svn_repos/Src/DocBeam/Clients" > SVNListParentPath On > SVNAdvertiseV2Protocol Off > AuthzSVNReposRelativeAccessFile authz > </Location> > > <LocationMatch "^/svn/Src/DocBeam/Clients/[^/]+"> > AuthName "ams_svn_repos/Src/DocBeam/Clients" > AuthType Basic > PerlAuthenHandler HttpdAuthnHandler > Require valid-user > </LocationMatch> Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
