Karl Fogel wrote:
>Jeff Putsch <putsch@mxim.com> writes:
>
>
>>I appreciate the fact the subversion allows both HTTP style (in the URL) and
>>--username/--password style authentication. Unfortunately if either
>>authentication fails subversion falls back to prompting the user
>>for username and/or password.
>>
>>I am trying to write a specialized wrapper around subversion and
>>would prefer to have subversion never fall back to interactive queries.
>>
>>Is there a way to prevent it from doing that?
>>
>>
>
>Not yet, but it would be pretty easy to add a --non-interactive long
>option (it could also be a ~/.subversion/config option, though that's
>less important than having it available via the command line for
>scripts).
>
>My gosh, this is so easy, I think I'll just do it now.
>
>
Please don't ... aargh, you already have. I think this was a bad move.
It's better to fix the code than to add yet another option: If you
already passed a --username and --password, or if your url is
http://user:pass@foo/..., then why on earth would you have to pass
--non-interactive to suppress the password dialogue, too? That just
doesn't make sense -- we're beginning to accumulate one-shot options at
an alarming rate. And not writing tests for them, may I add.
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 6 05:06:36 2002