As the number of backend ssl providers for curl increased, it became more convenient to switch to use expand flags for them. As of curl-7.25.0-r1, USE="ssl" means that one and only one of CURL_SSL="openssl -axtls -cyassl -gnutls -nss -polarssl" must be chosen, with openssl being the default if none is given. This means that packages that use depend on curl's ssl may have to change. Packages which simply depend on net-misc/curl[ssl] are fine. But those that wish to specify which of the ssl backends to use, must now do so in use expand form. So for example, net-misc/curl[ssl,gnutls] should become net-misc/curl[ssl,curl_ssl_gnutls]. This is a tracker bug to alert maintainers of packages which use dep on curl[ssl] with some specific backend. While I haven't looked, this might also be a good time to check if you really need to pick a particular backend ssl for your package because net-misc/curl[ssl] works fine and is backward compat.
Grepping through the tree shows the following packages are effected: dev-libs/libcaldav net-libs/liboauth sci-misc/boinc sys-auth/pam_pkcs11 www-client/firefox-bin net-im/centerim net-libs/libmicrohttpd
(In reply to comment #1) > sci-misc/boinc I maintain a local overlay for boinc, as boinc relies on curl with openssl but not gnutls, am I correct in assuming the ebuild should read || ( <net-misc/curl-7.25.0-r1[ssl,-gnutls] >=net-misc/curl-7.25.0-r1[ssl] )
(In reply to comment #2) > (In reply to comment #1) > > sci-misc/boinc > > I maintain a local overlay for boinc, as boinc relies on curl with openssl > but not gnutls, am I correct in assuming the ebuild should read > > || ( <net-misc/curl-7.25.0-r1[ssl,-gnutls] >=net-misc/curl-7.25.0-r1[ssl] ) Yes, that should work. As atracker, discussion for each particular packages should happen in their respective bug. For boinc, bug #412437.
(In reply to comment #3) > (In reply to comment #2) > (In reply to comment #1) > > sci-misc/boinc > > > I maintain a local overlay for boinc, as boinc relies on curl with openssl > > but not gnutls, am I correct in assuming the ebuild should read > > || ( > <net-misc/curl-7.25.0-r1[ssl,-gnutls] >=net-misc/curl-7.25.0-r1[ssl] ) Yes, > that should work. As atracker, discussion for each particular packages > should happen in their respective bug. For boinc, bug #412437. Apologies, I didn't see that bug until after I had replied - and then instantly I guessed I had done wrong but couldn't see a delete button - [chatter ended]
I think EAPI=4 allows a more elegant solution than what is suggested in the various bugs. A package which works exclusively with openssl uses now net-misc/curl[ssl,-gnutls,-nss] and could use in the future net-misc/curl[ssl,-gnutls(-),-nss(-),curl_ssl_openssl(+)] without resorting to multiple versioned dependencies.
02 Aug 2012; Diego E. Pettenò <flameeyes@gentoo.org> +pam_pkcs11-0.6.8.ebuild, -pam_pkcs11-0.6.6.ebuild: Version bump (new EAPI, new curl dependencies, more documentation installed, silent build introduced upstream and disabled in ebuild). Remove old.
