public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New USE_EXPAND flag for www-servers/monkeyd
Date: Tue, 28 May 2013 14:57:03 -0400	[thread overview]
Message-ID: <51A4FDFF.3020103@gentoo.org> (raw)
In-Reply-To: <20130528173513.50742051@gentoo.org>

On 05/28/2013 11:35 AM, Michał Górny wrote:
> On Mon, 27 May 2013 16:38:09 -0400
> "Anthony G. Basile" <blueness@gentoo.org> wrote:
>
>> I was about to add a use expand flag for monkeyd (a tiny web server) and
>> there is a notice in base/make.default to discuss use expand flags on
>> the list first.  There are about 9 plugins for monkeyd similar to apache
>> which can be turned on/off by a configure switch. It makes sense to
>> follow the same logic as apache here.  There are no dependencies on
>> monkeyd and so no use-deps.  Seems very safe. Any objections?
> Could you elaborate a bit more on the flags? Please list them, shortly
> explain and tell us whether you expect the number of plugins to expand
> and how fast.
>

Sorry I already committed this with Chainsaw's ack.  Anyhow, they are:

auth - Provide HTTP Basic Authentication
cheetah - Provide a shell-like command line interface
#cgi - Provide the traditional CGI interface
dirlisting - Show an HTML listing of the content of a directory
#fastcgi - Provide FastCGI proxy support
liana - Build your own network layer through monkeyd
logger - Log requests and common errors
mandril - Restrict incoming connections based on the IP address or URI 
request
polarssl - Provide HTTPS using PolarSSL v1.*.

The ones that are commented out are global flags and so I did not make 
them part of the USE_EXPAND, they are still treated as plugins by 
monkeyd and I have them commented out in monkeyd_plugins.desc with an 
explanation.  Upstream has an entire plugin system which they use 
extensively and expect contributors to use plugins.  There have always 
been a couple of changes with each bump, eg between 1.1.1 and 1.2.0 
regarding ssl.  So I expect the same in the future.

-- 
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail    : blueness@gentoo.org
GnuPG FP  : 1FED FAD9 D82C 52A5 3BAB  DC79 9384 FA6E F52D 4BBA
GnuPG ID  : F52D4BBA



  reply	other threads:[~2013-05-28 18:57 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 [this message]
2013-05-28 19:07     ` Michał Górny
2013-05-28 19:22       ` Anthony G. Basile
2013-05-28 20:18         ` Michał Górny
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=51A4FDFF.3020103@gentoo.org \
    --to=blueness@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mgorny@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