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

Re: SVNParentPath depth question

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2006-12-06 17:11:04 CET

On 12/5/06, Pev <pev@audiogeek.co.uk> wrote:
> Hi all,
> This may be an obvious answer but here goes anyway! :-) I've
> currently got an svnserve style Subversion server running and
> use a collection of repositories on a per-customer and per-project
> basis (so I can archive them independantly). i.e. :
> /svn_repositories/customer1/project1/
> /svn_repositories/customer1/project2/
> /svn_repositories/customer2/project1/
> /svn_repositories/customer2/project2/
> My question is this ; I'm experimenting with moving to use an
> Apache server configuration. However, to do things simply I'd
> like to use SVNParentPath to avoid adding each repository to
> and from httpd.conf by hand at creation time. However, as far
> as I can tell SVNParentPath only works with projects a single
> level below the directory, and hence if I specify for my
> server :
> SVNParentPath /svn_repositories
> I can't pick up the two level structure as above. Is this a
> fixed limit or is there something I can do to work around
> this?

Yes, it is a fixed limit: mod_dav_svn iterates over all paths in the
given directory, determining whether the given directory is a working
copy or not.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 6 17:12:30 2006

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.