On Fri, 8 Jun 2007, James Dennett wrote:

>> I agree with this as well. The older libssh2 is so old that I don't really
>> see any point with us trying to support that if it comes with a cost like
>> #ifdefs. Let's cut that out and instead make the configure check for
>> libssh2 >= 0.15.
>
> Would (and should) that be done before or after libssh2 0.15 is released?

I think we can make libcurl only support >= 0.15 even before libssh2 0.15 is
released, yes, since I believe it'll be quite painful to support both the 0.14
interface as well as the new fancy non-blocking 0.15 without the libcurl code
getting unreadable with #ifdefs.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html