Just a reminder about putting this functionality in APR, in case some people in this thread aren't aware:
When we discover some functionality that would ideally be provided by APR but isn't, such as this, then we should write it in such a way that it is suitable for inclusion in APR (except for needing an "apr_" prefix instead of "svn_"), and then after we've got it into Subversion we can then propose it to the APR project and there is a good chance that it will be accepted. Then we make our configury use the APR implementation if available and our own implementation if an older APR is being used. A long time later, we stop supporting the older versions of APR and then delete our implementation. - Julian On Tue, 2011-06-07 at 02:11 +0300, Daniel Shahaf wrote: > Peter Samuelson wrote on Mon, Jun 06, 2011 at 16:25:01 -0500: > > > > [Daniel Klíma] > > > I tested it and same result. However I found something relevant in MSDN > > > library: > > > http://msdn.microsoft.com/en-us/library/7x2hy4cx.aspx (Console and Port > > > I/O) > > > > Thanks! I still believe we should do our prompting on the console, > > instead of stdin/stderr - especially stdin should be free for use by > > 'svnadmin load', 'svn patch' and the like. Does anyone here still > > think we should support the case of trying to 'drive' the interactive > > prompts in command-line programs, programmatically? AFAIK, we've never > > officially supported that sort of thing (especially password prompts), > > and I don't see a need. > > > > I don't know whether we 'supported' it or not, but the ASF Infrastructure > team uses internally a tool that programmatically answers svn(1) > password prompts. > > (but for that use case, I believe we will be okay regardless of whether > the password prompt reads from stdin or from the controlling terminal) > > > I'll come up with a patch using the Win32 functions from that article, > > when I find the time, which probably won't be today. > >
