On 12/6/06, Erik Huelsmann <ehuels@gmail.com> wrote:
> 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.
BTW: If you want it changed, you can submit a patch and see how others
feel about this.
bye,
Erik.
---------------------------------------------------------------------
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:13:34 2006