Re: Stefan Fritsch 2011-05-03 <201105032258.02556.sf@sfritsch.de> > I am not sure what problem you want to solve, exactly. AFAIK, there is > no package that exclusively depends on a threaded MPM. Therefore, you > can simply install apache2-mpm-prefork and have no dependency > problems. For each instance, you can still use whatever MPM you want > via the APACHE_HTTPD variable in the /etc/apache-xxx/envvars file. Am > I missing something? Or should the documentation be clearer? For a customer site, we need to be able to install apache2-mpm-prefork and apache2-mpm-worker at the same time. Currently, this doesn't work because of the Conflicts and hence the APACHE_HTTPD is of no use for us. > In any case, Apache httpd 2.4 will have MPMs as dynamic modules, which > will likely result in the apache2-mpm-* packages going away > completely. Therefore, I don't want to spend any effort on those > packages. We will most likely be using backports from backports.debian.org, so we would even benefit from 2.2 packages that are co-installable. At the moment we have to use patched packages which we would like to avoid. I'm putting Martin Zobel-Helas on Cc who is working with the customer. I won't have time for the next weeks to work on this, maybe he can provide a patch. Christoph -- cb@df7cb.de | http://www.df7cb.de/
Attachment:
signature.asc
Description: Digital signature