Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58330
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.42 as permitted sender)
Received-SPF: pass (google.com: domain of julienpauli@gmail.com designates 10.14.28.16 as permitted sender) client-ip=10.14.28.16;
MIME-Version: 1.0
Sender: julienpauli@gmail.com
In-Reply-To: <CAEZPtU6a9F5kt7hTOgstHcyei6HNO2t=BPnKThwwmFAP=Y=Kjg@mail.gmail.com>
References: <CAORXhGJWoLbLgX4ur_CuYpj7J28srgBtcO7uTnM5Wt5SYwKD9w@mail.gmail.com>
 <5a1d155ad465d1ec2e6461f5347d859f.squirrel@www.l-i-e.com> <CAMUwpuS+17YjUzpZ7PYj-G4Bh6NjqkH-ZN2zOcC_J9JXRrQqUw@mail.gmail.com>
 <4F4BF1C6.8010104@rowe-clan.net> <4F4C23CB.30402@oracle.com>
 <4F4D05FE.607@rowe-clan.net> <4F4D2EBA.6000409@oracle.com>
 <4F4D49ED.2020104@php.net> <4F4D5535.7000309@rowe-clan.net> <CAEZPtU6a9F5kt7hTOgstHcyei6HNO2t=BPnKThwwmFAP=Y=Kjg@mail.gmail.com>
Date: Wed, 29 Feb 2012 10:43:35 +0100
Message-ID: <CAMUwpuQtegKpF0f1BrR36OYq7PaH-vhDswEOCaf8RFQxv9ttuw@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Cc: "William A. Rowe Jr." <wrowe@rowe-clan.net>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=bcaec521555dc4b52504ba172fcd
Subject: Re: [PHP-DEV] pecl, zts, non-zts, fastcgi and Apache
From: jpauli@php.net (jpauli)

--bcaec521555dc4b52504ba172fcd
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Feb 29, 2012 at 9:18 AM, Pierre Joye <pierre.php@gmail.com> wrote:

> hi Bill,
>
> On Tue, Feb 28, 2012 at 11:29 PM, William A. Rowe Jr.
> <wrowe@rowe-clan.net> wrote:
> > On 2/28/2012 3:41 PM, Sebastian Bergmann wrote:
> >> On 02/28/2012 02:44 PM, Christopher Jones wrote:
> >>> Build PHP with ZTS enabled by default. Allow it to be explicitly
> >>> disabled during 'configure'
> >>
> >>  Why punish everyone by default because of Apache? Does not make sense
> to
> >>  me.
> >
> > What is so difficult to grok about
>
> Nothing, but it is easier to get a point when the rhetorical comments
> are removed :)
>
> >  1. setting up php-cgi to use fastcgi as the httpd default.
> >
> >  2. having parallel non-zts and zts installs of php (notably with only
> >    non-zts cli and cgi sapi's) with two different lib paths.  Multiply
> >    by two again if you have parallel i686 and x86_64 installs.
> >
> > All of these are packager's questions anyways, as so few users do this
> > for themself, most hosters aren't rebuilding php either.
>
> Right, and that's a rather big change, package wised. While the
> lbraries (systems) are the same, at lest for 99.99% of them. There are
> a few which can be built in TS or not TS mode but I don't think it is
> worth it.
>
> > PHP would be a much nicer, friendly and more civilized development list
> > if it borrowed only one phrase from the Perl community; TMTOWTDI.
>
> Civilized sounds very wrong in this context, or in general these days.
>
> Cheers,
> --
> Pierre
>
> @pierrejoye | http://blog.thepimp.net | http://www.libgd.org
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Right, I suggest we leave #61172 as is, as it solves the problem.
PHP should be built with whatever MPM has been detected at configure time
(httpd -V) , and that's all.

The work of switching MPM later should be left to package maintainers, and
scripts like Debian's "a2enmod" which can handle that themselves.

Just my thoughts :)

Julien.P

--bcaec521555dc4b52504ba172fcd--