libsoup statically links to openssl when selected, gnutls ssl doesn't. I'm not sure if it's supposed to do that or not, the configure help suggests not. I don't think it's a good thing to link static by default when not really needed for a good reason.
Foser, is this still applicable in the latest version?
a simple ldd of the libsoup lib should give the requested, but i don't have openssl support, so I can't tell right now.
Gnome people, if I'm not mistaken this problem is not applicable to the 2.x ebuilds. Is that correct?
correct 2.x uses gnutls exclusively, it was a problem with openssl.
So what does this mean? That 1.99.x should be fixed? that 2.x should be marked stable on all arches? that this bug can be closed? any permutation of the above?
ideally 1.99 should still be fixed, but I don't think it's worth spending the time. 1.99 & 2 are slotted different so we can't use the one for the other.
What happens is that if libsoup-1.99.x is compiled against openssl, it creates an auxiliary binary, /usr/libexec/libsoup-ssl-proxy which is the component linked to the openssl shared library. If libsoup is compiled against gnutls, no such proxy is created, and libsoup-2.0.so is linked directly.
