loudmouth can use openssl for ssl support without any drawbacks. But it uses a different configure switch for turning openssl on(--with-ssl=openssl), so the ebuild needs a change. I'll attach an ebuild with "gnutls" as a new USE flag.
Created attachment 135195 [details] loudmouth-1.2.3.ebuild + gnutls USE flag
Comment on attachment 135195 [details] loudmouth-1.2.3.ebuild + gnutls USE flag This dependencies are broken; you shouldn't depend on something that's not going to be used.
fix in CVS if you have ssl + gnutls, gnutls will be compiled, if ssl only, openssl will be compiled. thanks for reporting.
(In reply to comment #3) > fix in CVS > > if you have ssl + gnutls, gnutls will be compiled, > The above is not working if openssl is already installed. Portage 2.1.3.19 and 2.1.4.4. # emerge -C gnutls # emerge -pv =loudmouth-1.2.3 [ebuild U ] net-libs/loudmouth-1.2.3 [1.0.1] USE="gnutls%* ssl -debug -doc -test%" 0 kB [0=>1]
sorry I don't get your point. When I'm talking about "having ssl or gnutls", it's about having USE flags enabled. In this aspect, the output you pasted looks perfectly normal to me. gnutls is the default. For what it's worth, it has been reported to me that loudmouth compiled with openssl doesn't work as well as with gnutls so I might decide to remove that flag anyway when I come around testing the problem.
I guess I was trying to raise the point that loudmouth is not correctly depending on gnutls when USE="ssl gnutls". If I have those useflags and gnutls is not already installed, the loudmouth build will fail. Ignoring any issues with openssl, gnutls is a dependency of loudmouth when those useflags are defined and is not being installed.
oh right, I can see it now. I've checked the ebuild and it's an ugly error of mine. I'll fix it asap.
should be fixed now. Please reopen if it's not the case.
