On Tue, 28 May 2013 15:22:04 -0400 "Anthony G. Basile" wrote: > I thought about ssl but I'm still not sure if USE=ssl means just openssl > or any ssl. Eg, with curl, which has a choice of one of six backend ssl > providers, I changed USE=ssl to mean that one and only one of the six > must be on. Previously though, USE=ssl in curl meant only openssl which > was confusing because you could also have USE=nss or gnutls etc provide > your ssl. monkey also bounced around its ssl backend from liana_ssl to > polarssl which is what made me think of curl. What if in the future > there's yet another ssl backend? Although use.desc does say ... "ssl - > Adds support for Secure Socket Layer connections". Any advice here? Any SSL. If there are multiple backends to support, there are specific flags which affect the choice but USE=ssl means any SSL is suitable. > monkeyd is intended for embedded systems which is why it has switchable > plugins. You can even choose whether or not to install the shared lib > and include files to really slim it down. I can understand using USE flags to trim down plugins (assuming they're large). But shared-lib is an overkill. If people want this degree of scalability, it's either INSTALL_MASK or USE=minimal. -- Best regards, Michał Górny