From: Arfrever Frehtes Taifersar Arahesis <arfrever.fta@gmail.com>
To: Gentoo Development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Add USE_EXPAND for apache
Date: Sat, 24 Nov 2007 20:42:01 +0100 [thread overview]
Message-ID: <200711242042.30351.Arfrever.FTA@gmail.com> (raw)
In-Reply-To: <200711241951.50144.hollow@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
2007-11-24 19:51:23 Benedikt Böhm napisał(a):
> the current behaviour of the apache ebuild -- chosing built-in modules based
> on /etc/apache2/apache-builtin-mods -- is very aweful, especially for binary
> packages.
>
> Therefore, i would like to add APACHE2_MODULES and APACHE2_MPMS to USE_EXPAND.
What with static modules? Will they be available?
> Currently, there are over 60 modules available in apache. Out of these, a good
> default would look like this IMO:
>
> APACHE2_MODULES="actions alias auth_basic auth_digest authn_alias authn_anon
> authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile
> authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate
> dir disk_cache env expires ext_filter file_cache filter headers include info
> log_config logio mem_cache mime mime_magic negotiation rewrite setenvif
> speling status unique_id userdir usertrack version vhost_alias"
You could also add access_compat, authn_core and authz_core.
--
Arfrever Frehtes Taifersar Arahesis
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-11-24 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 18:51 [gentoo-dev] Add USE_EXPAND for apache Benedikt Böhm
2007-11-24 19:42 ` Arfrever Frehtes Taifersar Arahesis [this message]
2007-11-24 20:29 ` Benedikt Böhm
2007-11-25 4:33 ` Josh Saddler
2007-11-29 8:46 ` Josh Saddler
2007-11-29 11:19 ` Benedikt Böhm
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=200711242042.30351.Arfrever.FTA@gmail.com \
--to=arfrever.fta@gmail.com \
--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