Hello, I'd like to ask for an advice related to net-im/ekg2 ebuild. I would like to switch the ebuilds there to use the primary autotools build system for the package, and the last thing on my to-do list is adding a 'ssl' flag to the package.
The package consists of a core application and a set of plugins which are built in a single run and build of which can't be easily separated from the core application build (and I'd like to avoid forcing upstream to split it). The package configure scripts checks for both GnuTLS and OpenSSL as a SSL backend. However, the use of a particular backend is plugin-specific. In particular, both Jabber and remote plugins support using either GnuTLS or OpenSSL as the SSL backend. If both are available (enabled), GnuTLS is preferred and used. On the other hand, the IRC plugin supports OpenSSL only, and the sim plugin relies on OpenSSL. 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. Right now, the ebuild uses 'gnutls' and 'openssl' flags to control enabling each of the backends. To simplify that for the user, I'd like to add a 'ssl' flag as well. The question is -- how should that flag behave, taking care of the situation I described above? -- Best regards, Michał Górny
signature.asc
Description: PGP signature
