Ryan Vordermann wrote on Sat, Feb 16, 2013 at 19:00:34 -0700:
> Daniel,
>
> Thank you for prompt response. I'm sorry I haven't returned the
> courtesy. I'm a full time student and I work with two jobs. One of
Busy man!
> them is closing on the ship date for their first product so things are
> busy. I copied and pasted material from your first email, to put the
> answer into one. Is that okay?
>
Yeah there's some latitude when replying to split or join multiple posts
into one reply. The points to keep in mind are threaded MUAs + "one
logical change per commit" (or the equivalent for mail threads that have
diverged into multiple topics).
> On Fri, Feb 1, 2013 at 11:31 AM, Daniel Shahaf <d...@daniel.shahaf.name>
> wrote:
> > Daniel Shahaf wrote on Fri, Feb 01, 2013 at 19:15:04 +0200:
> >> > want to support any of the other security features. What are the
> >> > appropriate values for the following arguments to this function?
> >> >
> >> > svn_cmdline_create_auth_baton
> >> >
> >> > Currently I have this:
> >> > svn_boolean_t non_interactive = FALSE;
>
> >> Basically this is "may prompt". The "plaintext" and "SSL certificate"
> >> prompt depend on this.
>
> OH. Does this part depend a call back then for the prompt?
>
Your English doesn't parse. Anyway, the code (somewhere in libsvn_subr)
will not call the "plaintext prompt" if "non_interactive" is TRUE.
> >> > const char *config_dir = NULL;
> >> > svn_boolean_t no_auth_cache = FALSE;
> >> > svn_boolean_t trust_server_cert = FALSE;
> >>
> >> Like the corresponding arguments to the cmdline binary.
> >>
> >> > svn_config_t *cfg_config = NULL;
> >> >
> >> That's the parsed "config" file from CONFIG_DIR. I'm not quite sure why
> >> we have both this and 'const char *config_dir'.
> >>
> >> (Also, where do you see the name "cfg_config"? It's called "cfg" at the
> >> declaration and definition, in trunk.)
>
> At this point I'm not sure anymore, but I *think* it was something I
> read in the source for the command line.
>
I see. I suppose the context was having cfg_config and cfg_servers,
i.e., in code that deals with both ~/.subversion/{config,servers}.
> >> > Which so far works, but I was just taking a WAG.
> >>
> >> Did you read the API documentation? Was it not clear?
>
> Not at the time. I was being a bad person. My advisor said "Add this
> feature" and five minutes later, it was so. Since nothing crashed I
> just ran with it at the time. I think I get this section now though.
>
> Thank you Daniel!
You're welcome.
Daniel
