Re: Binary pecl packages - general questions
| From: | Wez Furlong | Date: | Mon, 12 Sep 2005 17:39:23 +0000 |
| Subject: | Re: Binary pecl packages - general questions | ||
| References: | 1 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-2910@lists.php.net to get a copy of this message | ||
On 9/12/05, Sascha Kettler <kettler@gmx.net> wrote:
> 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?
I think the name has meaning for the installer, so if Greg says
crack_dll, it's probably for a good reason.
> Next thing is whether it is ok to put the .dll files into CVS aswell
There's no good reason to put those into CVS.
> 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).
Sounds useful to expose that information.
> 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
The numbers are actually the dates on which the API changed (or the
dates when we released a version with a changed API)
--Wez.