[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: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2003-04-09 09:40:41 CEST

--On Tuesday, April 8, 2003 9:09 AM -0500 cmpilato@collab.net wrote:

> Svnlook exists in C for ease of installation. To *require* swig and
> python bindings just to get a really basic repos looker tool is silly,
> IMO.

I consider myself lucky if I get the SWIG python bindings to compile about
half the times I compile SVN itself. I usually give up in frustration. I
think there is some overestimation on how many people are actually building
the bindings without problems. I think the template feature is useful enough
to always be available without fighting SWIG or Python. (Hello, SWIG/Python
bindings on Windows? Ha-ha.)

Furthermore, by exposing it at the API level, it allows new GUIs to be able to
deliver this functionality at essentially zero additional cost. That's a good
thing, I think. By removing this from the API, new GUIs will not have a way
of adding this feature (consistently).

Personally, the templates make it so I have to do one less step when creating
my repositories. I don't care much what SourceForge or *cough* any other
system does - those monkeys get paid lots of $$ to deal with it. I want
something that I don't *need* to write shell scripts to customize it.

SVN is there to scratch my needs not anyone else's. =) (I feel like Branko.)
-- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 9 09:41:36 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.