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

Re: mod_dav_dvn+SVNParentPath with non-repo subdirs

From: Branko Čibej <brane_at_apache.org>
Date: Sat, 21 Sep 2019 19:53:34 +0200

On 11.06.2019 20:15, Thorsten Schöning wrote:
> Hi all,
> I'm hosting SVN-repos using svnserve and by providing the argument
> "--root" with the parent dir of all my repos. In the past, all repos
> have been placed as a direct child of the given path, but recently I
> refactored that to manage repos by customers, topics and stuff. This
> works pretty easy with svnserve as it simply forwards all URLs given
> by clients into the file system, so one can really simply move repos
> into additional subdirs and those get published instantly.
> This doesn't work with mod_dav_svn:
>> Using this syntax, Apache will delegate the handling of all URLs
>> whose path portions begin with /svn/ to the Subversion DAV provider,
>> which will then assume that any items in the directory specified by
>> the SVNParentPath directive are actually Subversion repositories.
> http://svnbook.red-bean.com/en/1.8/svn.serverconfig.httpd.html
> https://stackoverflow.com/questions/2701915/svn-multiple-repositories-in-subfolders

Indeed, svnserve's --root option has a completely different meaning; it
restricts the search for repositories to a specific subtree of the
filesystem. SVNParentPath requires all repositories to be in one directory.

> I was unable to find reasons and discussions about why things are
> implemented differently,

It's most likely due to hysterical ... pardon me, historical reasons.

> if changes have already been suggested etc.
> Currently I'm placing a lot "SVNParentPath" in the config of my httpd,
> but would be great if one could reduce that in future.
> So, is there a reason why mod_dav_svn doesn't support additional
> subdirs? Is that likely to be changed?

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.

Because of these compatibility issues, it's possible that we couldn't
just change the semantics of SVNParentPath but would have to invent a
third option (SVNRoot?).

> Is it likely that svnserve will stop supporting addiitonal child dirs?


-- Brane
Received on 2019-09-21 19:53:43 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.