From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev-return-1823-arch-gentoo-dev=gentoo.org@gentoo.org>
Received: (qmail 12821 invoked by uid 1002); 14 Mar 2003 09:18:33 -0000
Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:gentoo-dev@gentoo.org>
List-Help: <mailto:gentoo-dev-help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev-unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-dev-subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@gentoo.org
Received: (qmail 4266 invoked from network); 14 Mar 2003 09:18:33 -0000
From: Benjamin Podszun <ben@galactic-tales.de>
To: "Thomas T. Veldhouse" <veldy@veldy.net>
Cc: absinthe@gentoo.org, gentoo-dev@gentoo.org
In-Reply-To: <002c01c2e9fd$b3bad9c0$1000a8c0@VELDYT>
References: <20030313203129.51b80d1e.bain@tcsn.co.za>
	 <020c01c2e9be$68754890$96d8399d@VELDYT> <1047625298.5449.6.camel@localhost>
	 <200303140220.18647.absinthe@gentoo.org>
	 <002c01c2e9fd$b3bad9c0$1000a8c0@VELDYT>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-rakLG86yxS26CcdYxHPs"
Organization: 
Message-Id: <1047633326.1455.6.camel@localhost>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2- 
Date: 14 Mar 2003 10:15:26 +0100
Subject: Re: [gentoo-dev] dev-php/mod_php-4.3.1-r1 compile fails
X-Archives-Salt: daff448d-c0c9-4b43-a81f-60476c4e903c
X-Archives-Hash: 19c3a4f92bb5fd030c1c47851909c529

--=-rakLG86yxS26CcdYxHPs
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

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 do=
n't
> see one and I have not seen any reports of it since the release of 4.3.
>=20
> Tom Veldhouse
>=20
> >
> > I disagree.
> >
> > It's production ready enough for RedHat, SuSE.  We should be able to ma=
ke
> > it work.
> >
> > Cheers,
> > Dylan Carlson
> >
> > Public Key: http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0x708=
E165F
> > Key fingerprint =3D 3AEA DE38 FE42 15A6 C0E2 730E 3D04 BCC1 708E 165F
> >
> >
>=20
>=20
> --
> gentoo-dev@gentoo.org mailing list
>=20

--=-rakLG86yxS26CcdYxHPs
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA+cZ2ueGGfskjv0zURAl6CAKCDKsBuIyxngvsQK+XbEivBWvemlgCeLptD
W0jMj9fX2AeIkUdAlE8euL0=
=dnLS
-----END PGP SIGNATURE-----

--=-rakLG86yxS26CcdYxHPs--