From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: blueness@gentoo.org
Subject: Re: [gentoo-dev] New USE_EXPAND flag for www-servers/monkeyd
Date: Tue, 28 May 2013 22:18:56 +0200 [thread overview]
Message-ID: <20130528221856.18343d12@gentoo.org> (raw)
In-Reply-To: <51A503DC.4080200@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]
On Tue, 28 May 2013 15:22:04 -0400
"Anthony G. Basile" <blueness@gentoo.org> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
next prev parent reply other threads:[~2013-05-28 20:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 20:38 [gentoo-dev] New USE_EXPAND flag for www-servers/monkeyd Anthony G. Basile
2013-05-28 6:01 ` Tony "Chainsaw" Vroon
2013-05-28 11:30 ` Anthony G. Basile
2013-05-28 6:24 ` René Neumann
2013-05-28 15:35 ` Michał Górny
2013-05-28 18:57 ` Anthony G. Basile
2013-05-28 19:07 ` Michał Górny
2013-05-28 19:22 ` Anthony G. Basile
2013-05-28 20:18 ` Michał Górny [this message]
2013-05-31 13:23 ` Gilles Dartiguelongue
2013-05-28 22:15 ` William Hubbs
2013-05-30 11:23 ` Ralph Sennhauser
2013-06-01 17:41 ` William Hubbs
2013-06-01 18:00 ` Michał Górny
2013-06-01 20:20 ` William Hubbs
2013-06-01 20:26 ` Michał Górny
2013-06-02 0:21 ` William Hubbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130528221856.18343d12@gentoo.org \
--to=mgorny@gentoo.org \
--cc=blueness@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox