[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: <cmpilato_at_collab.net>
Date: 2003-04-08 16:09:07 CEST

Greg Stein <gstein@lyra.org> writes:

> But hey... by this argument, I'll just go delete svnlook. It's a lot of
> complex code creating a maintenance burden. It's a needless, dormant bug
> source in Subversion, and it uses C code for tasks which are more easily and
> flexibly done in scripting. Blecch -- me no like :-)
> And hey, Mike and I have even ported it from C to Python. It is demonstrably
> replaceable by scripts, so why does it exist in C?

[Not weighing in on the repos template debate ... just rebutting
 Greg's exaggerated conclusion here]

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,

And about using C code for tasks more easily done in scripting? I
think our C code can handle path construction just fine without too
much pixie dust. Don't overstate what svnlook does -- half of the
subcommands just print property values, trivially accessible via the
svn_repos interface. The rest just prints nodes in a linked list.
The only really ugly subcommand is 'diff'.

All that said, once our bindings are fully and reliably handled in our
build system (on all platforms), once they've matured enough, and once
I'm convinced that Swig is becoming more widespread in its usage, I'd
be *completely* willing to discuss the permanent replacement of
svnadmin and svnlook with Python scripts! :-)

[I now return you to your regularly scheduled argument]

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 8 16:13:31 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.