"Jay 'Whip' Grizzard" <firstname.lastname@example.org> writes:
> > I mean... look at the world of CVS. Administrators create lots of CVS
> > repositories. There are automated systems out there that create lots
> > of CVS repositories too. I have *never* heard of a complaint along
> > the lines of, "damn, I wish 'cvs init' could automatically lay out the
> > repository for me from a template.".
> Know why you don't hear those complaints? CVS doesn't need any sort of
> real 'repository' structure to work well, beyond what is needed to store
> and build the source.
> Subversion, on the other hand, essentially _requires_ a directory structure
> be in place at the start to be _AT ALL USEFUL_. If you don't have some sort
> of 'meta' directory structure in place above whatever it takes to store
> and build your project, you lose most of the power of Subversion.
Oops, miscommunication here. :-)
I was talking about the feature which already exists in our C API --
namely, the ability for svn_repos_create() to build an "on disk"
structure from a template. These are real files and directories, like
the automatic installation of hook-scripts.
You're talking about a not-yet-implemented feature, the ability to
create an "in repos" structure (/branches, /tags, /trunk) from a
> > It's just not a common problem. I know the itch is intense for
> > gstein, but I think he's imagining other people have this itch too,
> > when it seems (to me) like people just don't. Automated scripts that
> > create repositories do many things, and the template feature doesn't
> > noticeably reduce the complexity of the task.
> Okay, quick ... who here uses roughly the same layout for every Subversion
> repository they create? I know I do ... I use /trunk /branches /tags and
Do you also wish that a specific set of hook scripts and a standard
DB_CONFIG file were automatically copied from a template? Just
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Apr 8 23:11:33 2003