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

Re: The `on_disk' and `in_repos' templates.

From: Branko Čibej <brane_at_xbc.nu>
Date: 2003-04-10 10:44:38 CEST

I almost blundered into this discussion about pros and cons of
integrated template support, but then realised there are enough opinions
flying around already. So I'll just bring up a few points that I think
need consideration, regardless of whether the template support is built
in or scripted

    * Installation. Where are the templates installed, on various
      systems? Do you have a single set of templates, or separate sets
      for different project groups?

    * Integration. Does the default repository (on-disk) layout remain
      hard-coded, or does it gradually move into the on-disk templates?
      What does such a move do to ease of installation?

    * Maintainability. How do you maintain/modify the templates? How do
      you document them? What tools do you need (e.g., for locating the
      template installation, etc.)

    * Filesystem features (for in-repos templates). What features of the
      filesystem can you control with the templates? Directory layout,
      properties, revprops?

    * Back-end features (for on-disk templates): Again, what features of
      the on-disk structure can you control with the templates? Thinking
      ahead, can the template idea be extended to non-Berkeley
      back-ends? What about DB_CONFIG or equivalent configuration files?
      Does the template determine the back-end type, or the other way

In short, what I'm asking for is a design discussion, starting with
basic requirements. Templates of any kind are potentially a very useful,
but also potentially large, feature. Let's not make the same mistake
with templates as we made with the working copy, where we just sort of
bunched ideas together into code until it all beame an unmaintainable mess.

Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 10 10:45:28 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.