Hi,
I guess my complaint is that the addition of a new feature has made
something that has worked fine for years and years and years just stop. I
get bitchy about that sometimes :-) This one in particular still _really_
irks me;
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450758
Anyway, up to you if you want to forward it upstream or not. I'll
update all of my scripts to use --non-interactive ... I'm curious how many
people this will bite when the new version of subversion ends up in debian
stable...
Thanks,
Tyler
Peter Samuelson <[EMAIL PROTECTED]> wrote:
>
> [Tyler MacDonald]
> > When subversion is being run without a controlling terminal (eg; "svn up <
> > /dev/null", or when being executed from a cronjob), subversion should
> > realize that it has no controlling terminal and revert to the previous
> > default behaviour, "postpone".
>
> The official view: any time you want to run svn from a script, you
> should be using --non-interactive. Sure, it seems you can sometimes
> skip it, but the set of circumstances that will use interactive
> behavior may change over time, so it is best not to assume you know
> which commands need this and which do not.
>
> You seem to be asking for Subversion to call isatty(0) and if it
> returns false, assume --non-interactive. I am not sure if that's a
> good idea. Upstream may resist this on the grounds that it isn't
> necessarily portable to Windows (though it should work on any Unix).
> --
> Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
