Re: non-interactive user authentication

Karl Fogel wrote:

>Branko Čibej <brane@xbc.nu> writes:
>
>
>>Now, none of this is a problem ina purely interactive environment. The
>>problems we're discussing only show up when the "svn" command is being
>>scripted. A simple way out is to simply say that any script that's
>>complex enough to have to bother with authentication should use the
>>swig wrappers instead. :-)
>>
>>
>
>s/simple/wrong/ :-).
>
:-)

>Anyway we're not talking about very complex scripts here -- we're
>talking about scripts that run 'svn update'. I've already got at
>least three of those.
>
>
I have a few of those, too -- some of them do updates from repositories
that require authentication for reading, not just for writing. I get by
by either explicitly passing --password, or setting things up so that
the auth info is populated in the working copies. If they're not very
complex scripts, then I guess it's to be expected that they requre
pretty precise set-up.

-- 
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