On Wed, 01 Dec 2010 22:44:45 +0100 Diego Elio Pettenò <flamee...@gmail.com> wrote:
> 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. Pure GnuTLS. > 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… Well, I thought about having 'ssl' to enable SSL support through OpenSSL and 'gnutls' to enable GnuTLS for the plugins supporting it. Then, logically, 'openssl' flag would be useful no more but wouldn't that imply exceeding the meaning of the 'ssl' flag? > How feasible would be to get upstream to implement GnuTLS support on > the remaining plugins? For the IRC plugin, it's pretty possible. For the sim plugin, I think it would be much harder. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
