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

Re: svn commit: r1422706 - in /subversion/trunk/subversion: libsvn_subr/opt.c tests/cmdline/svntest/main.py

From: Stefan Sperling <stsp_at_elego.de>
Date: Mon, 17 Dec 2012 21:32:24 +0100

On Mon, Dec 17, 2012 at 09:14:42PM +0100, Branko Čibej wrote:
> That "blatant abuse" happens at least in two places that I'm aware of:
> our tests, and Emacs vc-mode.

There is a difference between scraping the cli output and having
a program type answers into prompts. Do our tests really do the latter?

Anyway, we can always add a --force-interactive option for such use.

> And we'd hardly go to the trouble of keeping the command-line output
> backwards-compatible if we didn't /expect/ people to drive svn this way.

I'm generally opposed to favouring scriptability of the CLI over
interactive use of the CLI.

In this case, however, I'd like to make simple scripting easier by
preventing the need to add --non-interactive to every invocation of
'svn' in a script. You can surely see the advantage of that, no?

FWIW, every release since 1.6 has broken scripts that parsed CLI output in
a naive way. All these difference were documented in the release notes.
And we offer --xml mode and bindings with stable interfaces.
Received on 2012-12-17 21:33:07 CET

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.