[snip]
> > 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.
Okay, okay, I'll eat my foot now. :>
I actually thought this originally, and then you started talking about
"I don't hear cvs admins complaining that there's not a built-in way to set
up their repositories" (etc) and my mind went the wrong way.
> You're talking about a not-yet-implemented feature, the ability to
> create an "in repos" structure (/branches, /tags, /trunk) from a
> template.
Yep. Which still doesn't change all that much of my message, since it
looks like a lot of folks want to kill off that feature, too (rather than
making it actually work).
> Do you also wish that a specific set of hook scripts and a standard
> DB_CONFIG file were automatically copied from a template? Just
> wondering.
Well, I do think that some things (e.g. a database-trimming post-commit
hook) should be automagically copied from a default template of some sort;
The 'basic' repository really should be useful to as many people as general,
and right now, that does require some things to be in your standard
repository that just aren't there now.
Of course, the need for 'standard' hook scripts could be reduced/eliminated
with changes in subversion (e.g. move bdb log handling internal, just to
pick a particularly well-beaten horse), which makes the argument weaker,
but I'd still hate to see the idea go away completely.
-jay
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 9 01:28:29 2003