On Tuesday 02 of August 2005 17:55, I wrote:
So it is my proposition:
INCLUDE_PATH=.:/etc/php:/usr/local/share/php/5.0:/usr/share/php5:/usr/share
/php/5.0:/usr/share/php:/usr/local/share/php
EXTENSION_DIR=/usr/local/lib/php/5.0/20041030:/usr/lib/php5/20041030:/usr/l
ib/php/5.0/20041030:/usr/local/lib/php
BTW, there is mess about phpapi-NNNNNNNN virtual package. In fact there is
ZEND_EXTENSION_API_NO, ZEND_MODULE_API_NO, and PHP_API_VERSION. The first is
used by PHP extensions, the second by Zend extensions, the third... I don't
remember :) Now, extensions packages depends on phpapi-20041030 virtual
package.
Cite:
php5 (5.0.4-3) unstable; urgency=low
* And fix the module/extension API situation one last time, this time
we read ZEND_EXTENSION_API_NO, ZEND_MODULE_API_NO, and PHP_API_VERSION,
pick the most recent of the three, assume things broke in ways we're
not willing to cope with, and both change the extension directory to
use that value, as well as setting it to the provides/depends for the
various SAPI and extension packages.
* Add a new option to php-config, 'php-config --phpapi', which extension
packagers should now be using to get the current phpapi they're building
against and set their dependencies accordingly.
I don't like it... It is confused as far as phpinfo reports:
PHP API => 20031224
PHP Extension => 20041030
Zend Extension => 220040412
and seems to me that there could be problems in future if some of their values
will change breaking the YYYYMMDD scheme. Should I report the bug? I think
the packages should just provide separate virtual packages, i.e.:
Package: php5.0-cli
Provides: phpapi-20031224, zendmoduleapi-20041030, zendextensionapi-220040412
Package: php5.1-cli
Provides: phpapi-20041225, zendmoduleapi-20050617, zendextensionapi-220050617