Binary pecl packages - general questions
| From: | Sascha Kettler | Date: | Mon, 12 Sep 2005 15:22:27 +0000 |
| Subject: | Binary pecl packages - general questions | ||
| Groups: | php.pecl.dev | ||
| Request: | Send a blank email to pecl-dev+get-2906@lists.php.net to get a copy of this message | ||
Hi,
I've prepared my crack extension for a binary release for Windows, but I
have some general questions open for discussion:
What should the Windows binary package be called? Greg suggested crack_dll,
but I think crack_win32 would also be suitable. Is there any style fixed
yet?
Next thing is whether it is ok to put the .dll files into CVS aswell (I
currently compile my extension for every ZEND_MODULE_API_NO since 4.1.0)? I
know CVS does not handle binary files that well, but the individual .dll
files will be around 40k each.
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).
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
4.2.1 to 4.4.0: 20020429
5.0.0 to 5.0.2: 20040412
5.0.3 to 5.0.5: 20041030
5.1.0: 20050617
Yours,
Sascha Kettler