[gentoo-user] Apache 2 + portage

[gentoo-user] Apache 2 + portage

[dexters84]

Hi

I'm a little confused as long as new Apache use flags are concerned. 
With old Apache versions ( pre 2.2.6) all valid flags shown in
*emerge -pv Apache*
could have been set in /etc/portage/package.use in following format
*www-servers/apache flag flag -foo -bar flag*
and life was great :)

Unfortunately with the new version the concept changed. Some flags 
contain *% *some contain* ** and some both (not sure what it is for) - I 
only know that flags enclosed like this *(flag)  *are the one I have 
selected before.

My main problem is that emerge apache command is not affected by flag 
settings in /etc/portage/package.use in any way.
How do I properly set new apache flags ?
Where do I define APACHE2_MODULES ?
Where do I define APACHE2_MPMS ?

regards
dexter
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] Apache 2 + portage

[Lobotomia]

2008/3/2, dexters84 <dexters84@gmail.com>:
>  My main problem is that emerge apache command is not affected by flag
>  settings in /etc/portage/package.use in any way.
>  How do I properly set new apache flags ?
>  Where do I define APACHE2_MODULES ?
>  Where do I define APACHE2_MPMS ?

as defined in http://www.gentoo.org/doc/en/apache-upgrading.xml
you can use APACHE2_MODULES an APACHE2_MPMS  in /etc/make.conf

if you upgrade from version > 2.2.6-r4 you can use this two shell line:

echo APACHE2_MODULES=\"$(sed
'/^mod_/s/mod_\(.*\)\s\+\(shared\|static\)/\1/;t n;d;:n'
/etc/apache2/apache2-builtin-mods)\" >> /etc/make.conf

rm /etc/apache2/apache2-builtin-mods



-- 
"Per il giovane ribelle
non c'è soluzione..."
http://lobotomiatbm.wordpress.com
http://www.pettinix.org
http://pettinatoridibambole.blogspot.com
--
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] Apache 2 + portage

[Alan McKinnon]

On Sunday 02 March 2008, dexters84 wrote:
> Hi
>
> I'm a little confused as long as new Apache use flags are concerned.
> With old Apache versions ( pre 2.2.6) all valid flags shown in
> *emerge -pv Apache*
> could have been set in /etc/portage/package.use in following format
> *www-servers/apache flag flag -foo -bar flag*
> and life was great :)
>
> Unfortunately with the new version the concept changed. Some flags
> contain *% *some contain* ** and some both (not sure what it is for)
> - I only know that flags enclosed like this *(flag)  *are the one I
> have selected before.

That's not an Apache thing - it's an emerge display output thing.

See 'man emerge' in the --verbose section for details.
>
> My main problem is that emerge apache command is not affected by flag
> settings in /etc/portage/package.use in any way.
> How do I properly set new apache flags ?
> Where do I define APACHE2_MODULES ?
> Where do I define APACHE2_MPMS ?

Apache now pays attention to these flags:

     Installed versions:  2.2.8-r1(2)(14:59:42 02/03/08)
(apache2_modules_actions apache2_modules_alias 
apache2_modules_auth_basic apache2_modules_auth_digest 
apache2_modules_authn_anon apache2_modules_authn_dbd 
apache2_modules_authn_dbm apache2_modules_authn_default 
apache2_modules_authn_file apache2_modules_authz_dbm 
apache2_modules_authz_default apache2_modules_authz_groupfile 
apache2_modules_authz_host apache2_modules_authz_owner 
apache2_modules_authz_user apache2_modules_autoindex 
apache2_modules_cache apache2_modules_dav apache2_modules_dav_fs 
apache2_modules_dav_lock apache2_modules_dbd apache2_modules_deflate 
apache2_modules_dir apache2_modules_disk_cache apache2_modules_env 
apache2_modules_expires apache2_modules_ext_filter 
apache2_modules_file_cache apache2_modules_filter 
apache2_modules_headers apache2_modules_ident apache2_modules_imagemap 
apache2_modules_include apache2_modules_info apache2_modules_log_config 
apache2_modules_logio apache2_modules_mem_cache apache2_modules_mime 
apache2_modules_mime_magic apache2_modules_negotiation 
apache2_modules_proxy apache2_modules_proxy_ajp 
apache2_modules_proxy_balancer apache2_modules_proxy_connect 
apache2_modules_proxy_http apache2_modules_rewrite 
apache2_modules_setenvif apache2_modules_speling apache2_modules_status 
apache2_modules_unique_id apache2_modules_userdir 
apache2_modules_usertrack apache2_modules_vhost_alias doc ldap ssl 
threads -apache2_modules_asis -apache2_modules_authn_alias -apache2_modules_cern_meta -apache2_modules_charset_lite -apache2_modules_dumpio -apache2_modules_log_forensic -apache2_modules_proxy_ftp -apache2_modules_version -apache2_mpms_event -apache2_mpms_itk -apache2_mpms_peruser -apache2_mpms_prefork -apache2_mpms_worker -debug -selinux -sni -static -suexec)



-- 
Alan McKinnon
alan dot mckinnon at gmail dot com

-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] Apache 2 + portage

[Daniel Iliev]

On Sun, 02 Mar 2008 15:39:39 +0100
dexters84 <dexters84@gmail.com> wrote:

> Hi
> 
> I'm a little confused as long as new Apache use flags are concerned. 
> With old Apache versions ( pre 2.2.6) all valid flags shown in
> *emerge -pv Apache*
> could have been set in /etc/portage/package.use in following format
> *www-servers/apache flag flag -foo -bar flag*
> and life was great :)
> 
> Unfortunately with the new version the concept changed. Some flags 
> contain *% *some contain* ** and some both (not sure what it is for)
> - I only know that flags enclosed like this *(flag)  *are the one I
> have selected before.
> 

man -P 'col -b' emerge | grep -A11 "  --verbose"


> My main problem is that emerge apache command is not affected by flag 
> settings in /etc/portage/package.use in any way.
> How do I properly set new apache flags ?
> Where do I define APACHE2_MODULES ?
> Where do I define APACHE2_MPMS ?
> 
> regards
> dexter


I don't believe you could get a proper answer w/o sending the exact
output of the command(s) you're issuing and the relevant contents of the
configuration file(s) in question.


-- 
Best regards,
Daniel
-- 
gentoo-user@lists.gentoo.org mailing list