Stefan Sperling wrote:
> I also suspect that the first set of people (interactive CLI users)
> is larger than the second (script writers parsing CLI output), so
> more people will benefit if we have it enabled by default.
Fair enough. The problem is that by making the progress output on by default,
you are pretty much guaranteed to break every script that is currently parsing
the output. There is no way of knowing how many "embedded" scripts there are
out there in the wild, running in cron jobs, etc. I speak from experience in
that I have code at $WORK that relies on being able parse the output from
Subversion. I also have a set of modules on CPAN that would probably freak if
the output changed significantly. I don't have the time right now to convert
either to use the bindings (though it is in my long term plans).
If the wisdom of the combined developers decides that the risk of breaking code
outweighs the benefit to the CLI user, then I pretty much insist that there be
both a config file option to disable it, as well as the commandline option.
Besides, I thought someone already suggested that Hao Zhang spend his effort on
designing the callback hook as the GSOC project and only deal with the CLI
interface after that was completed.
John
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1442440
Received on 2009-03-27 11:57:51 CET