Hi Sandro,
Only based on what I know and given the current state of gnutls I would
just go with openssl for now. That matches how curl is currently
compiled at least.
shell~# curl --version
curl 7.18.2 (i486-pc-linux-gnu) libcurl/7.18.2 OpenSSL/0.9.8g
zlib/1.2.3.3 libidn/1.8 libssh2/0.18
Protocols: tftp ftp telnet dict ldap ldaps http file https ftps scp sftp
Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz
I don't know of a way to do both, you could do what Dima proposes but I
think you'd need to convince the curl maintainers to change curl-config
in both libcurl4-gnutls-dev and libcurl4-openssl-dev as well. Example:
so debian/rules can point to things like curl-config-openssl and
curl-config-gnutls or something.
I agree about licensing being better on gnutls but I'd rather have
functionality and reliability first, then licensing with multiple viable
options present. Maybe when a few things like this are squashed in the
libgnutls codebase then switch back over to it down the road.
Best Regards,
-Mike
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
