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

Re: [RFC] Design of svnvendor.py

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2006-05-20 00:34:55 CEST

Giovanni Bajo wrote:
> Also, *exactly because* the Subversion core MUST not know anything more than
> directories and versioned copies, I believe that this kind of "heuristic"
> must be done on external, layered tools. Maybe these tools are not useful
> for *everybody* using Subversion, true. But if they meet common usage
> patterns, that's enough to justify their existence, in my opinion.

Yes, that's right, and I think your proposal has a reasonable level of support
for different repository layouts: it makes the common cases easy and the
unusual cases possible.

Certainly it is good to make a utility as free of unnecessary restrictions as
possible, if it can still remain clean to use in the simple cases, so it is
well worth considering John's points, but I think he is being too pessimistic
in this case.

I feel many users re-invent or wish for many scripts to facilitate recommended
ways of working, and so I would like to see us gradually distribute more of
them, as long as we try to maintain some level of consistency (in style,
generality versus specificity, etc.) among them. Well-written utility scripts
can be extremely useful as examples or starting points for those who need
greater or different functionality, so they don't need to be capable of
handling every scenario.

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 20 00:35:25 2006

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