| 1 |
Actually the PHP guys say that it's on the one hand a problem with |
| 2 |
constant changes in the apache-api and on the other hand with making PHP |
| 3 |
work with the multi-threaded mpms. |
| 4 |
|
| 5 |
Doesn't matter for me, since I need apache only in combination with php. |
| 6 |
And you cannot rely on that with every apache2-configuration (read: |
| 7 |
mpm). |
| 8 |
|
| 9 |
Apart from that I don't see that problem in merging a masked package, if |
| 10 |
you're keen on apache2 ;) |
| 11 |
|
| 12 |
Dylan: |
| 13 |
We could chat a little about what Suse and RedHat thinks is |
| 14 |
production-ready (libc, gcc, kde .. They seem to love preleases..). |
| 15 |
Yes, apache2 is out and stable. I just pointed out that a lot of users |
| 16 |
will get into trouble if we make it the standard-httpd. Reasons: See |
| 17 |
above. If apache2 is unmasked and coexists with apache1.3 : Fine. |
| 18 |
If you want to upgrade (read: replace) 1.3: No, that's not an option for |
| 19 |
a lot of production environments. |
| 20 |
|
| 21 |
just my humble opinion. |
| 22 |
Ben |
| 23 |
|
| 24 |
On Fri, 2003-03-14 at 08:45, Thomas T. Veldhouse wrote: |
| 25 |
> Besides that, it is not a problem with Apache 2, it is a problem with |
| 26 |
> mod_php, if there is a problem at all. I don't think there is one. I don't |
| 27 |
> see one and I have not seen any reports of it since the release of 4.3. |
| 28 |
> |
| 29 |
> Tom Veldhouse |
| 30 |
> |
| 31 |
> > |
| 32 |
> > I disagree. |
| 33 |
> > |
| 34 |
> > It's production ready enough for RedHat, SuSE. We should be able to make |
| 35 |
> > it work. |
| 36 |
> > |
| 37 |
> > Cheers, |
| 38 |
> > Dylan Carlson |
| 39 |
> > |
| 40 |
> > Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F |
| 41 |
> > Key fingerprint = 3AEA DE38 FE42 15A6 C0E2 730E 3D04 BCC1 708E 165F |
| 42 |
> > |
| 43 |
> > |
| 44 |
> |
| 45 |
> |
| 46 |
> -- |
| 47 |
> gentoo-dev@g.o mailing list |
| 48 |
> |
Archives