On Sat, 25 Nov 2000, Domenico Andreoli wrote:

> > This is not as easy as it shounds. The php4-curl package is compiled with
> > libcurl0 installed. If it whould be binary compatible with libcurl0-ssl then
> > this package should probably Provide: libcurl0 . And I refuse to hardwire
> > dependency on a library, it's only calling for problems on other archs and
> > with autobuilders.
> >

> i'm just thinking at these problems.

> if libcurl0 and libcurl0-ssl were binary compatible i would do a virtual
> package and curl depending on this virtual one. same work for php4-curl.

What is libcurl0 and libcurl0-ssl?

> the matter is that i'm not sure they are binary compatible.

If these are libraries built with and without SSL, I can confirm that they
are "binary compatible". That is, if they're shared libraries, the same curl
binary can use either one of them.

> the upstream maintainer (whom i'm CCing to) said that curl knows nothing
> about ssl, everything is delegated to libcurl.

Exactly. Therefore, the curl tool has no idea if SSL is supported or not.
Only the libcurl in question does.

> something would break if if exchanged libcurl and libcurl-ssl under the
> same curl but i still don't figure out what.

Not if they're identically named and you have the ssl libs present when you
use the SSL version.

You could try this and see for yourself!

> now i have to solve the puzzle but i don't even know where to start from.
> suggestions?

I don't understand what the puzzle is all about.

-- 
  Daniel Stenberg -- curl project maintainer -- http://curl.haxx.se/