On Thu, Nov 17, 2011 at 05:39:37PM +0400, Sergey Skvortsov wrote:
> For example, our practice of layout organizing (simplified example):
>
> /svn
> /devops
> /infra
> /src
> /personal
> /user1
> /user2
> /project
> /prj1
> /prj2
>
> /svn, /svn/personal, /svn/project are folders.
> All the rest are repos.
>
> /src contains common code, used by almost all projects.
> /infra contains infrastructure stuff.
> /devops contains devops code/scripts/data.
>
> "user*" and "prj*" are especially made as separate repos by obvious reasons.
>
> Maybe you would recommend to move "/src" to "/common/src" and
> "/infra" to "/system/infra" and so on?
> But short URIs are cool, and typing long one's is too tedious.
In your scheme, a more elaborate apache config has the required result:
<Location /svn/devops>
SVNPath /var/svn/devops
...
</Location>
<Location /svn/infra>
SVNPath /var/svn/infra
...
</Location>
<Location /svn/personal>
SVNParentPath /var/svn/personal
...
</Location>
> So, disabling this useful feature seems like ungrounded restriction for me.
Yes, because you want to use a single SVNParentPath directive to
serve your top-level repositories and you think having one Location
statement per top-level repository is too much of a burden to maintain.
I can see your point but I don't think it's a very important issue.
If someone else wants to put in the effort into fixing this in mod_dav_svn
I won't object as long as the feature is properly implemented so people
don't shoot themselves in the foot when someone touches the configuration
(logging a warning is fine for this purpose). And a regression test must
be added to make sure your configuration doesn't break again.
Received on 2011-11-17 15:02:15 CET