Il giorno mer, 01/12/2010 alle 22.30 +0100, Michał Górny ha scritto: > > In other words, the preferred complete build of ekg2 requires both > gnutls and openssl. However, all of the features should work fine with > openssl itself as well. > There is a simple first question to ask here. Does it use pure GnuTLS or the GnuTLS-OpenSSL glue layer? If the latter, then you either build it to only use one, or you're going to hit symbol collisions which are no fun to debug.
In general, as much as I like to allow alternatives, I'd suggest you to pick a stand, and since OpenSSL is the lowest common denominator, I'd suggest you pick that one. But for sure there will be people complaining about licensing… How feasible would be to get upstream to implement GnuTLS support on the remaining plugins? -- Diego Elio Pettenò — “Flameeyes” http://blog.flameeyes.eu/ If you found a .asc file in this mail and know not what it is, it's a GnuPG digital signature: http://www.gnupg.org/
signature.asc
Description: This is a digitally signed message part
