Re: Binary versioning/compatibility of PECL modules

On Mon, 16 Jan 2006 15:59:23 -0800 Rasmus Lerdorf <rasmus@lerdorf.com> wrote: > Tim Jackson wrote: > > If I compile a PECL module, in what way(s) (if any) is it dependent > > on the version of PHP? > We bump the API version on binary breaks and your extension would > stop loading and would need a recompile. Typically this happens on a > x.y.z to x.y+1.0 PHP version bump. Thanks, Rasmus. As I thought - sounds like RPM (and other) packages for PHP need to encode a "Provides: php-api = VER" or something similar in them so that any PECL RPM packages can depend on this. Is that API this: $ php -i |grep "PHP API" PHP API => 20020918 ? If so, I'm a bit confused, because the above output is from 4.4.1, and I thought (in line with your x.y+1.0 explanation and the release notes for 4.4.0) that 4.4.x was a binary break from 4.3.x - but a copy of 4.3.9 I have around also has an API ver of 20020918. I presume main/php.h is the authoritative source for the API ver? Tim