I wish to have a multi-mpm-apache-ebuild (creating both a prefork-binary and a worker-binary). So I tested and verified that the modules bundled with the apache source tarball are binary-identical unaffected of my choice of the mpm (prefork or worker). This leads me to the conclusion that it should be possible to compile multiple apache2-binaries. Is there any argument against doing so? Otherwise i would create a patch for the apache-2.eclass and submit it here in the hope of that patch beeing added! Reproducible: Always
Created attachment 159105 [details, diff] Modified apache2-eclass that generates apache binaries for all mpms available
you generally can't mix threaded and non-threaded MPMs with most language interpreters (mod_php, mod_perl, etc) and it is generally not supported to build multiple MPMs
(In reply to comment #2) > you generally can't mix threaded and non-threaded MPMs with most language > interpreters (mod_php, mod_perl, etc) and it is generally not supported to > build multiple MPMs > This patch is required to provided both prefork & worker MPMs in the Apache binary package - for a BINHOST environment. We have many BINHOST client machines - some have prefork with mod_php and some use worker without any language interpreters.
I don't think it is a problem for the apache2 ebuild that language interpreters like php or python do not work with a threaded mpm properly! All bundled modules in the apache2 distribution work with both mpms! I think php, python, etc. should fix their builds (if needed!) and i think apache should not be restricted because other packages lack some features! And i am glad to see that at least on person thinks my patch is useful!
