Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32824
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender)
Message-ID: <4715B5FF.6000100@zend.com>
Date: Wed, 17 Oct 2007 00:13:03 -0700
Organization: Zend Technologies
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: sean finney <seanius@seanius.net>
CC:  internals@lists.php.net
References: <64ED731E-CA44-498E-9AF9-C9B00037B863@omniti.com> <200710151910.49707.seanius@seanius.net> <47155266.4010209@zend.com> <200710170848.23053.seanius@seanius.net>
In-Reply-To: <200710170848.23053.seanius@seanius.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Large file support for PHP
From: stas@zend.com (Stanislav Malyshev)

> but this wouldn't be any different from any other api/abi bump.  furthermore, 

Of course. If there are two different PHP versions with different API 
numbers, it's OK. What's less OK is when there's two PHP builds with 
same API numbers which are binary incompatible.

> in the context of running debian (and by extension ubuntu) servers, you 
> wouldn't need to do anything if you were only using the pre-packaged modules, 

You mean - pre-packaged by Debian?

> need to do an "apt-get upgrade", etc.  and if you were using other pecl 
> extensions, i think the command to update that isn't so complicated either :)

Compatibility is not complicated if you deal with one machine where you 
control everything and can rebuild everything from source. It starts to 
get worse when you have a lot of machines on which you want to achieve 
some kind of common environment. Having indistinguishable binary 
incompatible PHP versions complicates things.
-- 
Stanislav Malyshev, Zend Software Architect
stas@zend.com   http://www.zend.com/
(408)253-8829   MSN: stas@zend.com