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

Re: branches and tags [post v1.0]

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-10-17 18:13:20 CEST

Noel Yap <yap_noel@yahoo.com> writes:
> What you want can be easily solved with a wrapper. In
> fact, since Subversion doesn't require any particular
> repository structure, and any practical use of
> Subversion will require some sort of structure, I'm
> sure many people will write the same sort of wrappers
> and hooks. Maybe these can be contributed and placed
> into a contrib directory for others to reuse?

Heh! I'm so glad you brought that up.

The real motivation behind my restructuring of svnadmin's option
parsing (see revision 3258) was a plan to eventually add "layout
templates". That is, at Subversion install time, various directory
tree templates would be laid out in

   /usr/local/share/subversion/layouts/default/...
   /usr/local/share/subversion/layouts/asf/...
   /usr/local/share/subversion/layouts/slovenian/...

etc. Currently, the only one we know is "default", it's the standard

    /README
    /trunk/
    /branches/
    /tags/

repository layout. In other words, the template source would be this
nearly-empty directory tree:

   /usr/local/share/subversion/layouts/default/README
   /usr/local/share/subversion/layouts/default/trunk/
   /usr/local/share/subversion/layouts/default/branches/
   /usr/local/share/subversion/layouts/default/tags/

And to create a repository that looks like that, you'd just do

   $ svnadmin create /usr/local/repositories/main --layout=default

As people experiment and come up with other layouts that are tuned to
other situations, we'll just incorporate them into the distribution.
In other words, Subversion itself can serve as a central reference for
successful, time-tested repository layouts (hence the "asf" and
"slovenian" layouts... I don't know exactly what they'd look like, but
I'm sure they're excellent :-) ).

This isn't really necessary for 1.0, of course, but it's also easy to
code and it would be nice to have the structure in place early so
people have it available when creating their first repositories. Not
sure if/when I'll get around to it. Anyway, just wanted to mention it
here in case anyone had any thoughts.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 17 18:42:55 2002

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.