Charles A Edwards <[EMAIL PROTECTED]> writes: > On 14 May 2002 21:45:01 -0400 Jean-Michel Dault <[EMAIL PROTECTED]> > wrote: > > > Le mar 14/05/2002 � 14:10, Pixel a �crit : > > > > hum, that means some recompilation is needed... cuz of the new perl. > > > > > > maybe i should also put some "Conflict: apache-mod_perl <= > > >1.3.24_1.26-1mdk" in perl ? > > Yes, I think this is the best way, anyways people should never run Cooker > >for their production servers, Cooker breaks every now and then. > > > > mod_perl 2.0 will be out real soon now, to be in sync the new Apache 2. With > >mod_perl 1.99 it only compiles as a DSO, which creates segfaults with > >HTML-Embperl, Apache-ASP and HTML-Mason. > > > > Be prepared for a whole new bunch of conflicts for a month or so ;-) > > > > If "Conflict: apache-mod_perl <= 1.3.24_1.26-1mdk" in perl is implemented does > this not mean that other apps which require both apache And perl, such as > phpgroupware, will also be broken until such time as they can be rebuilt to > use apache2?
of course. The solution for this is to keep the old perl. It also means installations are broken. jmd, WYT just rebuilding mod_perl for now?
