Beside it's a requirement in order to make 389 Directory Server ebuilds I'm working on fully happy. It would be good to always have both mod_cgi and mod_cgid built as shared object for every selected MPM. Beside upstream discourages the usage of mod_cgi with multithreaded MPMs, the former can be used without problems, and in fact, 389 Directory Server (http://port389.org) is using apache that way. I think it would be a plus to let both modules be built as shared objects. Currently, when a multithreaded MPM is selected, mod_cgi is statically built, resulting in inability to disable/enable it via LoadModule directives (as upstream said). Reproducible: Always
Created attachment 237897 [details, diff] proposed eclass change This is the proposed apache-2.eclass change
Maybe it would be better/easier to use apache2_modules_cgi and apache2_modules_cgid USE flags?
...or move cgi/cgid modules compilation to apache2_modules_ use flags.
Yes, if you ack I can do it very quickly.
Created attachment 238223 [details, diff] make cgi cgid modules optional Here is the proposed patch, apache-2.2.15.ebuild should be revbumped and perhaps changes ported to 2.2.14 ebuild too. Let me know.
looks good, please feel free to fix it in cvs. with the upcoming multi-mpm support in apache 2.3 this makes much more sense too.
In CVS. Please review my changes anyway.
