[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] cleanup the neon socket when closing the ra_session

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2007-07-09 22:00:54 CEST

On 7/9/07, Dan Christian <dchristian@google.com> wrote:
> On 7/9/07, Joe Orton <joe@manyfish.co.uk> wrote:
> > On Mon, Jul 09, 2007 at 09:34:50AM -0700, Dan Christian wrote:
> > > <rant>
> > > How the @#@# was I supposed to know that should be defined?
> >
> > So far as neon goes: by running "man neon", reading NEWS from a 0.26.x
> > release tarball, or the reference docs linked from the web site;
> > specifically http://www.webdav.org/neon/doc/html/refneon.html
> Interesting, "man neon" talks about neon-config. This can tell you
> many things, but not if the library was built with
> --enable-threadsafe-ssl=posix.
> NEWS is not a source of configuration information! It's a source
> of... (wait for it :-)... news.
> refneon.html is quite helpful.
> My complaint is that I should never have to know to find/read the
> neon, serf, and openssl docs to properly link against subversion
> libraries! This should all be sanity checked at the subversion level
> (configuration and/or run time).

You would rather that we duplicate all documentation on the myriad
ways you can configure each of our dependencies? Yes, our docs could
be better on some of the common gotchas, and if you contributed a FAQ
on how to get things perfectly happy in a multithreaded build or a
patch to do the required runtime checking I'm sure it would be
committed, but expecting to never have to refer to the docs for one of
the packages that are required is really kind of a tall order, IMO.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 9 22:00:29 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.