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

Re: Standardised Repository Schema

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-04-16 18:22:42 CEST

"Kim Lester" <kim@dfusion.com.au> writes:

> I'd like to suggest that in the "Definitive Guide" we add
> some more explicit details about repository layout guidelines.

Actually, we've been planning to get more aggressive in the Book, and
recommend a very specific "standard" layout. (I agree with you -- we
don't want to fall into the X windows problem!)

Our recommendation is this: define a "project root" to be a URL to
the 'root' of some project. The URL could point to the top of a
repository, or it could point to some directory within a repository.
It doesn't really matter. The "official layout", then, is that a
project root *must* contain a /trunk, /branches, /tags area.

If you look at Subversion's own repository, we're already following
this pattern. The project roots within our repository are

   Subversion: http://svn.collab.net/repos/svn
   RapidSVN: http://svn.collab.net/repos/svn/clients/rapidsvn
   gsvn: http://svn.collab.net/repos/svn/clients/gsvn

...and so on.

So our Offical Recommendation works whether you want one project per
repository, or 10 projects per repository, or any combination thereof.

As I said, the three book authors are already planning to add these
ideas to the book.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 16 18:24:08 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.