[Yes, I know this thread is a week old.]
[John Peacock]
> I suppose we could try to have it default to ON if the process has a
> tty and OFF otherwise (which should deal with scripting), but knowing
> how the Subversion client libraries are designed, that information
> may be two or more call sites removed from where you'd want to know.
We already have precedent for breaking scripts. Remember when you
could do a simple 'svn update' in a post-commit hook? Now it will get
you in trouble, because by default it does interactive conflict
resolution. The solution is '--non-interactive'. And in fact we
encourage people to always use '--non-interactive' in scripts, even for
subcommands that are already noninteractive, because you never know
which subcommands may _become_ interactive in future releases.
That said, I would favor moving all of our interactivity to use
/dev/tty instead of stdin/stdout, and treat failure to open /dev/tty as
if --non-interactive had been passed. (And, well, I have no idea what
the Windows equivalent would be.)
--
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
Received on 2009-04-03 15:55:51 CEST