Re: Binary pecl packages - general questions
| From: | Greg Beaver | Date: | Mon, 12 Sep 2005 21:37:00 +0000 |
| Subject: | Re: Binary pecl packages - general questions | ||
| References: | 1 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-2912@lists.php.net to get a copy of this message | ||
Sascha Kettler wrote:
> It would probably be really great for the PEAR installer to be able to
> install binary extensions not using a PHP version but a ZEND_MODULE_API_NO.
> Currently this constant is not available inside PHP, but it can be easily
> extracted from the phpinfo() output. Also the DEBUG and ZTS flags would be
> great for installconditions (maybe just use something like
> 20020429-no-debug-zts as a match).
binary windows PECL packages should only be used for production, so I
don't think it is a good idea to support debug builds. As for ZTS, I
think you should only be bundling .dlls that will work with the official
PHP version as distributed at php.net. If your extension needs two
.dlls, include both and document that the user should add the proper one
to php.ini. There's no need for installer magic here
php_crack-zts.dll
php_crack.dll
would be fine.
What about zend_version()? Is this as useful as ZEND_MODULE_API_NO?
> The reason for this proposal is that the ZEND_MODULE_API_NO is not that
> consistent with the major PHP release number. The different versions I have
> seen are:
>
> 4.1.0 to 4.2.0: 20010901
PEAR 1.4.0 only supports PHP 4.2.0 and newer, so don't bother with
binary .dlls for earlier versions.
Greg