Currently it seems when installing apache-2.4.x on Gentoo without actively setting any MPM and using threads it sets the default to worker: The corresponding eclass code is this: if [[ -z "${MY_MPM}" ]] ; then if use threads ; then MY_MPM=worker However, the upstream default (at least on all major plattforms) is the event mpm. Is there any reason Gentoo moves away from the upstream default here? I think usually a user that doesn't set any MPM will expect it to be "the standard", which for apache 2.4 is event.
I agree with you on that but we should make sure to keep upstream's default for apache-2.2 as well. Do you happen to know if they default to worker mpm for apache-2.2?
I think in 2.2 event was considered experimental by upstream. But frankly, I don't really care as I would always recommend to avoid 2.2 if possible. But there's an obvious strategy here: Don't pass any mpm-options to the configure script if the user doesn't set anything. This will always choose the default, independent of the apache version.
(In reply to Hanno Boeck from comment #2) > But there's an obvious strategy here: Don't pass any mpm-options to the > configure script if the user doesn't set anything. This will always choose > the default, independent of the apache version. This would defeat purpose of the thread USE flag which I'm not willing to give up right now. I gonna change the eclass to use event worker for apache-2.4 in case thread USE flag is enabled and APACHE2_MPMS is empty or unset.
+ 22 May 2014; Lars Wendler <polynomial-c@gentoo.org> apache-2.eclass: + Eclass cleanup. Now requires >=EAPI-4 ebuilds. Fixed bugs #509922 and + #503640. +
