On 02/28/2012 02:29 PM, William A. Rowe Jr. 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
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.
PHP would be a much nicer, friendly and more civilized development list
if it borrowed only one phrase from the Perl community; TMTOWTDI.
These are useful suggestions for a future "bigger picture" direction
about sensible defaults, usability (or lack of), php-fpm, etc. This
is a problem looking for an owner.
In the narrow confines of https://bugs.php.net/bug.php?id=61172 the
packager has deliberately chosen to install mod_php. Like Sebastian,
I prefer that PHP configures itself for the currently installed Apache
MPM.
Chris
--
Email: christopher.jo...@oracle.com
Tel: +1 650 506 8630
Blog: http://blogs.oracle.com/opal/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
