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
package as well as other precompiled pecl packages available in the debian
archive. all of them are compiled against the same api, which is provided by
a php{4,5}-dev package, which you can install on your system if you want to
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 individual
sysadmin. i for one would do my utmost to avoid ever finding myself in a
situation where i was compiling php (or any other moderately complex
software for that matter) from source on more than a couple different
OS/architecuture/distribution combinations, and instead try to consolidate
things. for example, using the distributions' precompiled packages,
backported packages, 3rd party packages, compiling once and nfs-mounting,
rsyncing, etc. but anyway, this is maybe getting a little side tracked....
sean
signature.asc
Description: This is a digitally signed message part.
