Re: non-interactive user authentication

Remember that this all could apply to other commands as well (see the thread
about 'svn sync'). If svn decides to only prompt if authentication was not
explicitely provided on the command line, then what about other commands that
don't have any other way to turn off interactive mode? What about
alternative auth methods that don't use a user/pass scheme?

Keeping in mind the potential for other commands, I see three viable options:

(1) allow a --non-interactive switch

(2) commands are not interactive by default, and provide a --interactive (-i)
switch

(3) all commands are not interactive, period. Provide a p4-style interactive
shell as an alternative.

The third option is too restrictive for a user-interface client, even if it is
command line. So that leaves #1 and #2.

Taking into account user friendlyness, that pretty much leaves #1. With the
potential for other interactive commands, it's too messy to have some complex
heuristic determine whether enough information has been supplied explicitely
on the command line to turn off interactive mode.

Why not just have --non-interactive as a global option, make authentication
the first user of that option, and expect that future (non-)interactive
commands will come around (and they will)?

> Before I revert the change, let's all decide here what the behavior of
> the ... options should be.

-- 
Peter Davis
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org