Why we need to set SVNPatrh or SVNParentPath?

Hi,

I'm integrating Subversion with Sourceforge package (GForge). The goal is
that if some one create the 'tigris' project, the svn repository address
would be http://svn.tigris.sf.net.

The svn repository could be http://svn.*.sf.net.

We used the Virtual host configuration to support this:

<VirtualHost 128.114.63.154:8080>
       ServerName svn.ucsc.edu
       ServerAlias svn.*.ucsc.edu
       VirtualDocumentRoot /var/lib/gforge/chroot/home/groups/%2/svn
       <Location />
                DAV svn
       </Location>
</VirtualHost>

In this case, the SVNPath depends on the project name noted %2. For example,
The tigris SVN path would be /var/lib/gforge/chroot/home/groups/tigris/svn.
I can't set a static SVNPath or SVNParentPath in this case.

Why just guess a SVNPath from DocumentRoot and Location, if SVNPath and
SVNParentPath are not given. I'm sure there are many cases that we cannot
define a static SVNPath.

The patch is attached. This is tested and works. Using this patch, now I can
create a svn virtual host for each project.
I added a dav_svn_guess_fs_path function based on r->filename and root_path.
Since I have very little knowledge about Subversion, I'm not sure if this is
correct way to fix the problem.

Have a nice day

-
Sung Kim

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org