With CVS, if I want to create a new, separate project, and I have write
access to a given directory, I can do this:
cvs -dautarch@urth.org:/var/lib/cvs import foo initial start
and CVS will create a directory /var/lib/cvs/foo under which files for the
"foo" project can be checked in. This is entirely separate from the
/var/lib/cvs/bar directory for the "bar" project, and this is a good thing
if those projects have two different groups of developers, because the
permissions can be separate, branches and tags are separate, etc.
Now, with Subversion, to completely separate projects, I can create
multiple repositories under a filesystem directory like /var/lib/svn.
With a "SVNParentPath" directive to mod_dav_svn, I can make these all
accessible via HTTP(S) pretty easily, which is nice and slick. And of
course, I can use Apache config to manage read/write permissions for each
project.
But there's not way to "auto-create" a new repository. I still have to go
to the server and do "svnadmin create foo" to make a new, separate "foo"
project repository.
This is not a huge problem, obviously, but it might be nice to have way to
remotely create a new repository. One usage example might be one where
you are hosting Subversion repositories for multiple companies/groups of
developers. Each group of developers gets its own "SVN root directory",
under which they can have multiple projects. Rather than give every
developer a shell account on that one machine, or even give every
developer group an account, it'd be nice to have a mechanism to let them
remotely create a new repository. This is similar to the recent
discussion about creating parent paths when importing into an existing
repository, but a little different.
-dave
/*==================
www.urth.org
we await the New Sun
==================*/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 16 22:46:12 2002