On Tue, 28 May 2013 14:57:03 -0400 "Anthony G. Basile" <[email protected]> wrote:
> On 05/28/2013 11:35 AM, Michał Górny wrote: > > On Mon, 27 May 2013 16:38:09 -0400 > > "Anthony G. Basile" <[email protected]> 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.*. Shouldn't this one be tied to USE=ssl? For the others, how large is the benefit of having them switchable? At least some of them look like something that wouldn't hurt people if it was always-built. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
