Actually the PHP guys say that it's on the one hand a problem with
constant changes in the apache-api and on the other hand with making PHP
work with the multi-threaded mpms.

Doesn't matter for me, since I need apache only in combination with php.
And you cannot rely on that with every apache2-configuration (read:
mpm).

Apart from that I don't see that problem in merging a masked package, if
you're keen on apache2 ;)

Dylan:
We could chat a little about what Suse and RedHat thinks is
production-ready (libc, gcc, kde .. They seem to love preleases..).
Yes, apache2 is out and stable. I just pointed out that a lot of users
will get into trouble if we make it the standard-httpd. Reasons: See
above. If apache2 is unmasked and coexists with apache1.3 : Fine.
If you want to upgrade (read: replace) 1.3: No, that's not an option for
a lot of production environments.

just my humble opinion.
Ben

On Fri, 2003-03-14 at 08:45, Thomas T. Veldhouse wrote:
> Besides that, it is not a problem with Apache 2, it is a problem with
> mod_php, if there is a problem at all.  I don't think there is one.  I don't
> see one and I have not seen any reports of it since the release of 4.3.
> 
> Tom Veldhouse
> 
> >
> > I disagree.
> >
> > It's production ready enough for RedHat, SuSE.  We should be able to make
> > it work.
> >
> > Cheers,
> > Dylan Carlson
> >
> > Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F
> > Key fingerprint = 3AEA DE38 FE42 15A6 C0E2 730E 3D04 BCC1 708E 165F
> >
> >
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
>