hi Christoph,
On Fri, Mar 5, 2010 at 9:32 AM, Christoph Berg <m...@debian.org> wrote:
>> --- trunk/debian/control 2010-03-05 08:11:05 UTC (rev 131)
>> +++ trunk/debian/control 2010-03-05 08:13:39 UTC (rev 132)
>> -Depends: torrus-common (= ${source:Version}), apache2-mpm-worker | apache2,
>> libapache2-mod-perl2 (>= 2.0.0), libapache2-request-perl (>= 2.05-dev-6)
>> +Depends: torrus-common (= ${source:Version}), apache2-mpm-prefork |
>> apache2, libapache2-mod-perl2 (>= 2.0.0), libapache2-request-perl (>=
>> 2.05-dev-6)
>> +Conflicts: apache2-mpm-worker
>
> is that the right fix? There are two other MPMs, namely
> apache2-mpm-event and apache2-mpm-itk in Debian. If Torrus is only
> incompatible with -worker, I agree, but what about the others?
according to the MPM documentation, mpm-itk should work fine, but
mpm-event will most probably conflict in the same way as worker.
I would set it to conflict with mpm-event as well, until someone tests it.
I'm also thinking of implementing a new application handler, probably
it will be lighttpd+fastcgi.
thanks,
stan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
