The problem:
1) there's a directory on the server containing multiple svn
repositories roots, say /var/svn, with /var/svn/a, /var/svn/b, etc.
being repository roots
2) these repositories are accessed via HTTP, handled by Apache2 + mod_dav_svn
3) there's a MySQL user-password database we need to use
Yep, i could manage to get to such configuration, but here's when it
comes to the real difference with your setup: we need to manage a huge
and frequently changing user database, with each user having a small
repository.
>
> Here's the big caveat: whenever a repository is added or removed (in you
>
> This might be exactly what's needed if you're, say, teaching a programming
> class where you want students to learn to use Subversion for version control
> of their projects. You don't want students to be able to mess with each
> others' code, and you probably don't want to retain their data f
