Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32838
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain seanius.net from 66.93.22.232 cause and error)
To: Stanislav Malyshev <stas@zend.com>
Date: Wed, 17 Oct 2007 23:08:56 +0200
User-Agent: KMail/1.9.7
Cc: internals@lists.php.net
References: <64ED731E-CA44-498E-9AF9-C9B00037B863@omniti.com> <200710170848.23053.seanius@seanius.net> <4715B5FF.6000100@zend.com>
In-Reply-To: <4715B5FF.6000100@zend.com>
MIME-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart1757090.nJjiBfRy86";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-ID: <200710172308.59770.seanius@seanius.net>
Subject: Re: [PHP-DEV] Large file support for PHP
From: seanius@seanius.net (sean finney)

--nextPart1757090.nJjiBfRy86
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 17 October 2007 09:13:03 am Stanislav Malyshev wrote:
> 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.

right.

> > 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?

yeah.  there are a number of precompiled modules provided by the debian php=
=20
package as well as other precompiled pecl packages available in the debian=
=20
archive.  all of them are compiled against the same api, which is provided =
by=20
a php{4,5}-dev package, which you can install on your system if you want to=
=20
build your own modules as well.

> 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.

i'd say this has more to do with the administration habits of the individua=
l=20
sysadmin.  i for one would do my utmost to avoid ever finding myself in a=20
situation where  i was compiling php  (or any other moderately complex=20
software for that matter) from source on more than a couple different=20
OS/architecuture/distribution combinations, and instead try to consolidate=
=20
things.  for example, using the distributions' precompiled packages,=20
backported packages, 3rd party packages, compiling once and nfs-mounting, =
=20
rsyncing, etc. but anyway, this is maybe getting a little side tracked....


	sean

--nextPart1757090.nJjiBfRy86
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHFnnrynjLPm522B0RAhVkAJ9nAel6AGiXjrf10qIb70dN4FNbWgCfacfW
3fTlzG2jIjFCpdekPc30J3k=
=eph7
-----END PGP SIGNATURE-----

--nextPart1757090.nJjiBfRy86--