I have received a response from PECL developers regarding the latest CUBRID update at PECL SVN. Below are the messages from them.
Based on their comments we have to make several changes:
1. Indicate that this is not PHP 5 version API but PECL within phpdoc/en/cubrid/versions.xml file. We have to investigate more on this.
2. As I understood, users will need to install CUBRID using 'pecl install cubrid' command, in which case the documentation should be updated (simplified) within configure.xml.
Discuss this issues below.
Esen.
Email 1: On Sep 6, 2010, at 7:24 PM, Esen Sagynov wrote:
> cubrid Tue, 07 Sep 2010 02:24:05 +0000
>
> Revision: http://svn.php.net/viewvc?view=revision&revision=303119
>
> Log:
> update CUBRID PHP APIs doc according to version 2008 R3.0
>
> Changed paths:
> U phpdoc/en/trunk/reference/cubrid/versions.xml
…
I see the version numbers state "PHP 4, PHP 5". Isn't this a PECL only extension? I assume it did not come bundled with PHP 4, nor PHP 5, so think these are typos. If it's PECL only then it should state which PECL version said functions were introduced, although considering there are zero releases it should probably say "PECL Cubrid SVN". Thoughts? Any releases soon?
Regards,
Philip
Email 2: On Sep 7, 2010, at 6:16 PM, 에센 사그노브 wrote:
> Dear Philip,
>
> Thank you for you comments.
>
> Could you please clarify what does PECL only release mean? In fact, CUBRID API is for PHP 5.2 and above, that is PHP Connector for CUBRID Database. Do I miss something? Yesterday's SVN update for CUBRID API has considerable modifications based on PECL moderators' comments and suggestions. So, now it does, I hope, comply with PHP guidelines. Any further recommendations and suggestions are always welcomed.
To be clear, I'm only talking about phpdoc/en/cubrid/versions.xml file which lists the versions that functions became available. For PECL extensions, these list the version (PECL release) that they became available, so it might say "PECL >= Cubrid 0.4" if it was first created/released in version 0.4 of the PECL extension.
The first (strpos()) is part of PHP core, and has been since PHP 4. The second (apc_fetch()) is PECL only, as of the 3.0.0 release of the PECL APC extension. And NumberFormatter::create() is in both PHP core (as of 5.3.0) and in the PECL intl extension as of its 1.0.0 release.
Using these examples, Cubrid is PECL only (like APC) so it should reflect the versions that it became available within the extension itself. Currently that's SVN only but I assume it will be 0.1 or 1.0.0 or something like that, whatever you choose. Currently it says "PHP 5", which is incorrect.
> Considering the releases, I have a question. I have already created the CUBRID account at PECL http://pecl.php.net/package/CUBRID. And I wonder how should I make releases available at CUBRID account such as here http://pecl.php.net/package/xslcache? As you see they have a list of Available Releases. Could you please give me some help on it?
That's a question for the pecl-dev list, or the #php.pecl IRC channel on EFnet. Eventually all people will need to do is 'pecl install cubrid' in which case the documentation should be updated (simplified) within configure.xml.
Regards,
Philip
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I got a message from PECL moderators. They saw our new PECL package release and asked why did we have three consecutive releases. Check it out here under the subject http://news.php.net/php.pecl.dev.
I told this was kind of a test to check whether everything is working. This is what he replied.
Please don't do it this way. A release is a release, pecl.php.net is
not a test server.
You can always valid your packages using pecl install package-1.2.3.tgz.
As of windows, pecl install/update is not supported.
2010/9/14 에센 사그노브 <esen.sagynov@nhn.com>
>
> Hello Pierre,
>
> Have just tested out uploading the latest stable release for the CUBRID-PHP API to test installing it using the "pecl install cubrid" command. Have just tested on Linux with success. Now will try on Windows.
>
> If there are any questions, please let me know.
>
> Regards,
>
> Esen.
According to this email "pecl install cubrid" will not work on Windows. I didn't understand that why. Could you please check it out? And please be rational when uploading the new release, OK?
Have a good day!
Esen.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Client API version should the the PHP API version, in fact, not the CUBRID DBMS version. And the next time, let's not hurry with uploading the new release. Let's discuss together and them you upload, OK?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have check some other extension's info in phpinfo(). There seems to be no standard about version info.
In PECL package.xml, there are two kinds of version: release and api. So I use "Extension release Version" to indicate the Library release version, and use "Client API Version" to indicator the API version which can be used in the same version DBMS.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I have read the comments from PECL, and I will add config.w32 to our project. With this file, PECL extension can be compiled with PHP source codes.
And I have no idea if we should keep VC project files or should remove them? What do you think? Maybe we can keep them in sourceforge svn and remove them from PECL svn?
By the way, the Chinese wiki "CUBRID" has been updated, you can read it and check if it still needs improvement.
Use config.w32
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for Wikipedia page! That looks just awesome!
Concerning the VC project files, let's keep it. I am sure there will be many users who can benefit from it. So, keep it in the same /win directory. Anyway, it does not put on much weight to the package, right? I will also discuss about this issues on my side and get back to you soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello all,
I have received a response from PECL developers regarding the latest CUBRID update at PECL SVN. Below are the messages from them.
Based on their comments we have to make several changes:
1. Indicate that this is not PHP 5 version API but PECL within phpdoc/en/cubrid/versions.xml file. We have to investigate more on this.
2. As I understood, users will need to install CUBRID using 'pecl install cubrid' command, in which case the documentation should be updated (simplified) within configure.xml.
Discuss this issues below.
Esen.
Email 1: On Sep 6, 2010, at 7:24 PM, Esen Sagynov wrote:
> cubrid Tue, 07 Sep 2010 02:24:05 +0000
>
> Revision: http://svn.php.net/viewvc?view=revision&revision=303119
>
> Log:
> update CUBRID PHP APIs doc according to version 2008 R3.0
>
> Changed paths:
> U phpdoc/en/trunk/reference/cubrid/versions.xml
…
I see the version numbers state "PHP 4, PHP 5". Isn't this a PECL only extension? I assume it did not come bundled with PHP 4, nor PHP 5, so think these are typos. If it's PECL only then it should state which PECL version said functions were introduced, although considering there are zero releases it should probably say "PECL Cubrid SVN". Thoughts? Any releases soon?
Regards,
Philip
Email 2: On Sep 7, 2010, at 6:16 PM, 에센 사그노브 wrote:
> Dear Philip,
>
> Thank you for you comments.
>
> Could you please clarify what does PECL only release mean? In fact, CUBRID API is for PHP 5.2 and above, that is PHP Connector for CUBRID Database. Do I miss something? Yesterday's SVN update for CUBRID API has considerable modifications based on PECL moderators' comments and suggestions. So, now it does, I hope, comply with PHP guidelines. Any further recommendations and suggestions are always welcomed.
To be clear, I'm only talking about phpdoc/en/cubrid/versions.xml file which lists the versions that functions became available. For PECL extensions, these list the version (PECL release) that they became available, so it might say "PECL >= Cubrid 0.4" if it was first created/released in version 0.4 of the PECL extension.
Let's look at some examples:
(PHP 4, PHP 5)
http://php.net/manual/en/function.strpos.php
(PECL apc >= 3.0.0)
http://php.net/manual/en/function.apc-fetch.php
(PHP 5 >= 5.3.0, PECL intl >= 1.0.0)
http://php.net/manual/en/numberformatter.create.php
The first (strpos()) is part of PHP core, and has been since PHP 4. The second (apc_fetch()) is PECL only, as of the 3.0.0 release of the PECL APC extension. And NumberFormatter::create() is in both PHP core (as of 5.3.0) and in the PECL intl extension as of its 1.0.0 release.
Using these examples, Cubrid is PECL only (like APC) so it should reflect the versions that it became available within the extension itself. Currently that's SVN only but I assume it will be 0.1 or 1.0.0 or something like that, whatever you choose. Currently it says "PHP 5", which is incorrect.
> Considering the releases, I have a question. I have already created the CUBRID account at PECL http://pecl.php.net/package/CUBRID. And I wonder how should I make releases available at CUBRID account such as here http://pecl.php.net/package/xslcache? As you see they have a list of Available Releases. Could you please give me some help on it?
That's a question for the pecl-dev list, or the #php.pecl IRC channel on EFnet. Eventually all people will need to do is 'pecl install cubrid' in which case the documentation should be updated (simplified) within configure.xml.
Regards,
Philip
Here is the mailing list of PECL DOCS http://news.php.net/php.doc.cvs. You can see a message from Philip Olson at the bottom.
OK, I've got it, and I will update the doc soon.
Another comment from PECL member.
hi,
On Mon, Sep 13, 2010 at 2:19 AM, Esen Sagynov <cubrid@php.net> wrote:
> cubrid Mon, 13 Sep 2010 00:19:25 +0000
>
> Revision: http://svn.php.net/viewvc?view=revision&revision=303302
>
> Log:
> add how to install phpize; fix a mistake about extension_dir in section 2.3; add note in build-guide: when using VC9 CUBRID PHP Library, VC++ 2008 redistributable is needed
>
> Changed paths:
> @@ -148,6 +148,28 @@
> src> /usr/bin/phpize
> </pre>
>
> +<table border="0" bgcolor="silver"> <tr><td><pre class = "s1">
> +
> + <b>What is phpize? Where can I get it?</b>
All these things are well explained in the PHP documentation. What's
about pointing the users to it? It could be nicer than reproducing it
here :)
Cheers,
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
You can find the latest comment here http://news.php.net/php.pecl.cvs, particularly this one http://news.php.net/php.pecl.cvs/14690.
Hello Yifan,
I got a message from PECL moderators. They saw our new PECL package release and asked why did we have three consecutive releases. Check it out here under the subject http://news.php.net/php.pecl.dev.
I told this was kind of a test to check whether everything is working. This is what he replied.
Please don't do it this way. A release is a release, pecl.php.net is
not a test server.
You can always valid your packages using pecl install package-1.2.3.tgz.
As of windows, pecl install/update is not supported.
2010/9/14 에센 사그노브 <esen.sagynov@nhn.com>
>
> Hello Pierre,
>
> Have just tested out uploading the latest stable release for the CUBRID-PHP API to test installing it using the "pecl install cubrid" command. Have just tested on Linux with success. Now will try on Windows.
>
> If there are any questions, please let me know.
>
> Regards,
>
> Esen.
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
According to this email "pecl install cubrid" will not work on Windows. I didn't understand that why. Could you please check it out? And please be rational when uploading the new release, OK?
Have a good day!
Esen.
OK, I know, and I upload a new package just now. ^_^
The info displayed in phpinfo() has been changed:
CUBRID support Enabled
Client API Version 8.3.0
Extension release Version 8.3.0.100903
Wait,
Client API version should the the PHP API version, in fact, not the CUBRID DBMS version. And the next time, let's not hurry with uploading the new release. Let's discuss together and them you upload, OK?
OK.
I have check some other extension's info in phpinfo(). There seems to be no standard about version info.
In PECL package.xml, there are two kinds of version: release and api. So I use "Extension release Version" to indicate the Library release version, and use "Client API Version" to indicator the API version which can be used in the same version DBMS.
Since the Client API mean the PHP API, we have to indicate the PHP API version. And…
Supported CUBRID Server: 8.3.0
I understand. Then the info in phpinfo will be like this:
CUBRID support enabled
Client API Version 8.3.0.100914
Supported CUBRID Server 8.3.0
And you can install cubrid using pecl on Linux to check if there are problems during installation process.
If people of PECL see another release about CUBRID, maybe they will become angry. :)
That's why let's wait and make several changes and then after CUBRID 3.0 will be released we can upload a new release, OK?
OK. :)
Hello Yifan,
How have you been these days? Any news on your side?
Did you check the PECL CVS comments on your last changes? Take a look here
http://news.php.net/php.pecl.cvs/14721
Please post your updates if you have any.
Esen.
Hi, I have read the comments from PECL, and I will add config.w32 to our project. With this file, PECL extension can be compiled with PHP source codes.
And I have no idea if we should keep VC project files or should remove them? What do you think? Maybe we can keep them in sourceforge svn and remove them from PECL svn?
By the way, the Chinese wiki "CUBRID" has been updated, you can read it and check if it still needs improvement.
Use config.w32
Yifan,
Thank you for Wikipedia page! That looks just awesome!
Concerning the VC project files, let's keep it. I am sure there will be many users who can benefit from it. So, keep it in the same /win directory. Anyway, it does not put on much weight to the package, right? I will also discuss about this issues on my side and get back to you soon.
I have added config.w32 into PECL & cubridinterface svn. The test has been done on my own system with VC9 and SDK6.1.