Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
Pierre Joye in php.pecl.dev (Thu, 19 Sep 2013 09:14:16 -0700): On Thu, Sep 19, 2013 at 12:30 AM, Jan Ehrhardt php...@ehrhardt.nl wrote: Pierre Joye in php.pecl.dev (Fri, 30 Aug 2013 10:18:37 +0200): On Fri, Aug 30, 2013 at 8:51 AM, Jan Ehrhardt php...@ehrhardt.nl wrote: Pierre Joye in php.pecl.dev (Fri, 30 Aug 2013 07:38:20 +0200): On Thu, Aug 29, 2013 at 8:09 PM, Jan Ehrhardt php...@ehrhardt.nl wrote: I only do that if the release is already published at http://www.php.net/downloads.php but the announcement is delayed. The tagging of a release is only a sign for me that a release is imminent. The announcement makes it official, not the upload or the tagging :) Which is a bit odd. The announcement of 5.4.19 was about two days after it appeared on http://windows.php.net/download/ ... I really do not think it is a good thing to publish a build for a given non existent release., dixit Pierre. Are some pigs more equal than others? ;-) No, should have been done or updated at the same time. Will check that out. 5.5.4 and 5.4.20: http://windows.php.net/download/ ? They were once again published before the announcement. PHP 5.4.20 is at this moment still not announced and thus 'non existent'. Jan -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
On Thu, Sep 19, 2013 at 9:34 AM, Jan Ehrhardt php...@ehrhardt.nl wrote: They were once again published before the announcement. PHP 5.4.20 is at this moment still not announced and thus 'non existent'. It is due to mirroring issue. It is actually announced but not pushed yet. That's something somehow hard to sync at the exact same second. However we and the RMs are totally in sync about when it is ready to be pushed. Anyway, that does not a publication make 1-2 days before announcement any better. We may fix that at some point but it is not in a very high position in our todos. Cheers, -- Pierre @pierrejoye | http://www.libgd.org -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
On Thu, September 19, 2013 18:34, Jan Ehrhardt wrote: Pierre Joye in php.pecl.dev (Thu, 19 Sep 2013 09:14:16 -0700): On Thu, Sep 19, 2013 at 12:30 AM, Jan Ehrhardt php...@ehrhardt.nl wrote: Pierre Joye in php.pecl.dev (Fri, 30 Aug 2013 10:18:37 +0200): On Fri, Aug 30, 2013 at 8:51 AM, Jan Ehrhardt php...@ehrhardt.nl wrote: Pierre Joye in php.pecl.dev (Fri, 30 Aug 2013 07:38:20 +0200): On Thu, Aug 29, 2013 at 8:09 PM, Jan Ehrhardt php...@ehrhardt.nl wrote: I only do that if the release is already published at http://www.php.net/downloads.php but the announcement is delayed. The tagging of a release is only a sign for me that a release is imminent. The announcement makes it official, not the upload or the tagging :) Which is a bit odd. The announcement of 5.4.19 was about two days after it appeared on http://windows.php.net/download/ ... I really do not think it is a good thing to publish a build for a given non existent release., dixit Pierre. Are some pigs more equal than others? ;-) No, should have been done or updated at the same time. Will check that out. 5.5.4 and 5.4.20: http://windows.php.net/download/ ? They were once again published before the announcement. PHP 5.4.20 is at this moment still not announced and thus 'non existent'. Jan -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php Jan, that's also good so. If you look at the git history, what might happen is that a release is retagged. So even the tarballs were pushed to mirrors, they might have to change. The announce is the real deadline where no backspace is possible. If the release turns out to be erroneous after that, a new one has to go out. Regards Anatol -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
Anatol Belski in php.pecl.dev (Thu, 19 Sep 2013 20:39:01 +0200): that's also good so. If you look at the git history, what might happen is that a release is retagged. So even the tarballs were pushed to mirrors, they might have to change. The announce is the real deadline where no backspace is possible. If the release turns out to be erroneous after that, a new one has to go out. Suppose a new Wndows-user wants to install PHP. He goes to php.net, follows the link 'Windows 5.4.19 binaries and source' and finds only 5.4.20. What do you want him to do? Download a possibly erronous 5.4.20 or do you think he will go searching in http://windows.php.net/downloads/releases/archives/ for the latest 'real' release? Jan -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
On Thu, Sep 19, 2013 at 1:28 PM, Jan Ehrhardt php...@ehrhardt.nl wrote: Anatol Belski in php.pecl.dev (Thu, 19 Sep 2013 20:39:01 +0200): that's also good so. If you look at the git history, what might happen is that a release is retagged. So even the tarballs were pushed to mirrors, they might have to change. The announce is the real deadline where no backspace is possible. If the release turns out to be erroneous after that, a new one has to go out. Suppose a new Wndows-user wants to install PHP. He goes to php.net, follows the link 'Windows 5.4.19 binaries and source' and finds only 5.4.20. What do you want him to do? Download a possibly erronous 5.4.20 or do you think he will go searching in http://windows.php.net/downloads/releases/archives/ for the latest 'real' release? Jan, as I said earlier it is not 100% ideal but it is a matter for a couple of hours. We do not have a technical solution to solve that right now but as soon as there is something ready we will let you know. That being said, I still think it is something really different from using external builds only for the conveniences of having one huge set of extensions in the release. I think that instead of arguing about this problem we should discuss how to share our limited resources and provide everything at one place, using one procedure and without creating extra confusions with custom binaries (that we can't support when bugs are reported, I mean if we can't reproduce a bug for example). Cheers, -- Pierre @pierrejoye | http://www.libgd.org -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
Pierre Joye in php.pecl.dev (Fri, 30 Aug 2013 07:38:20 +0200): On Thu, Aug 29, 2013 at 8:09 PM, Jan Ehrhardt php...@ehrhardt.nl wrote: I only do that if the release is already published at http://www.php.net/downloads.php but the announcement is delayed. The tagging of a release is only a sign for me that a release is imminent. The announcement makes it official, not the upload or the tagging :) Which is a bit odd. The announcement of 5.4.19 was about two days after it appeared on http://windows.php.net/download/ ... I really do not think it is a good thing to publish a build for a given non existent release., dixit Pierre. Are some pigs more equal than others? ;-) Jan -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
On Fri, Aug 30, 2013 at 8:51 AM, Jan Ehrhardt php...@ehrhardt.nl wrote: Pierre Joye in php.pecl.dev (Fri, 30 Aug 2013 07:38:20 +0200): On Thu, Aug 29, 2013 at 8:09 PM, Jan Ehrhardt php...@ehrhardt.nl wrote: I only do that if the release is already published at http://www.php.net/downloads.php but the announcement is delayed. The tagging of a release is only a sign for me that a release is imminent. The announcement makes it official, not the upload or the tagging :) Which is a bit odd. The announcement of 5.4.19 was about two days after it appeared on http://windows.php.net/download/ ... I really do not think it is a good thing to publish a build for a given non existent release., dixit Pierre. Are some pigs more equal than others? ;-) No, should have been done or updated at the same time. Will check that out. -- Pierre @pierrejoye | http://www.libgd.org -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
Remi Collet in php.pecl.dev (Thu, 29 Aug 2013 08:07:28 +0200): Le 29/08/2013 00:27, Jan Ehrhardt a écrit : Given the current discussion I tried to build it under Windows (5.5 x86 NTS). Static failed, but shared worked. Yes I'm aware of an buld issue. As a PECL extension it can be build using bundled or system libjson-c AFAIK, there is no system libjson-c on Windows. If you merge it in the php tree (for static build), if will only build with system libjson-c (for now). I always merge all my extensions into the PHP-tree, using directory junctions (symlinks). The building of jsonc as static fails in the initial phases. Configure.js had no problem finding json_a.lib, but building later on stops with this message: main\internal_functions.c(72) : error C2065: 'phpext_jsonc_ptr' : undeclared identifier main\internal_functions.c(72) : error C2099: initializer is not a constant NMAKE : fatal error U1077: 'C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\cl.exe' : return code '0x2' It did not make any difference if I merged it as 'json' or as 'jsonc' into the PHP tree. Jan -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
29.8.2013 14:47, Jan Ehrhardt wrote: All of the 85 php extensions in my normal build script compiled as they used to. Result: https://dl.dropboxusercontent.com/u/8954372/php-5.5.3-nts-Win32-VC11-x86-jsonc.zip Jan Jan, Thank you for your hard work on awesome windows packages with a tons of useful extension built-in. These are regularly released shortly after official announcement. Especially apache2.2 handler for php 5.5 which isn't available in official php windows builds is very important for me. Keep on working Sir. M. Kubelik -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
hi! On Thu, Aug 29, 2013 at 5:25 PM, Jan Ehrhardt php...@ehrhardt.nl wrote: Miroslav Kubelík in php.pecl.dev (Thu, 29 Aug 2013 16:09:54 +0200): Thank you for your hard work on awesome windows packages with a tons of useful extension built-in. You can also get some here: http://windows.php.net/downloads/pecl/ snaps or releases which is about to be the place where pecl official binaries will be always be available, with links from pecl.php.net. These are regularly released shortly after official announcement. Especially apache2.2 handler for php 5.5 which isn't available in official php windows builds is very important for me. Hmmm. I would have sworn that php5apache2_2.dll for PHP 5.5 was provided by either Apachelounge or Apachehaus, but it is not. It seems to be lacking everywhere except in my builds. Because it is not supported anymore and there is very little reason to support it. For the curious people, I always announce new builds at http://www.apachelounge.com/viewforum.php?f=6 Most of the times within a few days after the official PHP release. And sometimes even a little bit before the announcement. Well, as there is nothing wrong to provide builds outside php, while it creates some real confusions from time to time in bug reports, I really do not think it is a good thing to publish a build for a given non existent release. Even if it is tagged, a release does not exist until it is announced. We have delayed releases many times in the past because of last minutes bugs, it does no one good to get a buggy version and to think everything is fine. Cheers, -- Pierre @pierrejoye | http://www.libgd.org -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
Pierre Joye in php.pecl.dev (Thu, 29 Aug 2013 19:59:01 +0200): Well, as there is nothing wrong to provide builds outside php, while it creates some real confusions from time to time in bug reports, I really do not think it is a good thing to publish a build for a given non existent release. Even if it is tagged, a release does not exist until it is announced. I only do that if the release is already published at http://www.php.net/downloads.php but the announcement is delayed. The tagging of a release is only a sign for me that a release is imminent. Jan -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
On Thu, Aug 29, 2013 at 8:09 PM, Jan Ehrhardt php...@ehrhardt.nl wrote: Pierre Joye in php.pecl.dev (Thu, 29 Aug 2013 19:59:01 +0200): Well, as there is nothing wrong to provide builds outside php, while it creates some real confusions from time to time in bug reports, I really do not think it is a good thing to publish a build for a given non existent release. Even if it is tagged, a release does not exist until it is announced. I only do that if the release is already published at http://www.php.net/downloads.php but the announcement is delayed. The tagging of a release is only a sign for me that a release is imminent. The announcement makes it official, not the upload or the tagging :) Cheers, -- Pierre @pierrejoye | http://www.libgd.org -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
Pierre Joye in php.pecl.dev (Wed, 12 Jun 2013 12:46:22 +0200): On Wed, Jun 12, 2013 at 12:36 PM, Remi Collet r...@fedoraproject.org wrote: Problem : Windows standard build have standard json build statically, so can't be disabled. I hope this could be possible in the future. Given the current discussion I tried to build it under Windows (5.5 x86 NTS). Static failed, but shared worked. Users expect it to be here, always, so I very much doubt we can provide it with shared json any time in a near future. Not only users, but other extensions rely on it as well. couchdb and couchbase are examples. And solr links directlly to ext/json: #include ext/json/php_json.h See http://svn.php.net/viewvc/pecl/solr/trunk/php_solr.h?view=markup Jan -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
Hi! Not only users, but other extensions rely on it as well. couchdb and couchbase are examples. And solr links directlly to ext/json: #include ext/json/php_json.h See http://svn.php.net/viewvc/pecl/solr/trunk/php_solr.h?view=markup This is another thing to consider. For a drop-in, at least public API (_API functions) should be there and compatible on source level. May be a bit of a challenge given the variety of options they have... -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
Le 04/06/2013 08:51, Jan Ehrhardt a écrit : PECL Announce in php.pecl.dev (4 Jun 2013 06:30:21 -): Support for JSON (JavaScript Object Notation) serialization. Package home: http://pecl.php.net/package/jsonc Would it be possible to support this extension under Windows? I took a look at the config.m4 and was discouraged by its complexity. No easy transform to a config.w32... version 1.3.1 will includes windows support (thanks to Anatol Belski). Binaries are available on http://windows.php.net/downloads/pecl/releases/jsonc/ Problem : Windows standard build have standard json build statically, so can't be disabled. I hope this could be possible in the future. Remi. Jan -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PECL-DEV] Re: [ANNOUNCEMENT] jsonc-1.3.0 (beta) Released.
On Wed, Jun 12, 2013 at 12:36 PM, Remi Collet r...@fedoraproject.org wrote: Le 04/06/2013 08:51, Jan Ehrhardt a écrit : PECL Announce in php.pecl.dev (4 Jun 2013 06:30:21 -): Support for JSON (JavaScript Object Notation) serialization. Package home: http://pecl.php.net/package/jsonc Would it be possible to support this extension under Windows? I took a look at the config.m4 and was discouraged by its complexity. No easy transform to a config.w32... version 1.3.1 will includes windows support (thanks to Anatol Belski). Binaries are available on http://windows.php.net/downloads/pecl/releases/jsonc/ Problem : Windows standard build have standard json build statically, so can't be disabled. I hope this could be possible in the future. Users expect it to be here, always, so I very much doubt we can provide it with shared json any time in a near future. That reminds me about a feature to disable static extensions, while the symbols conflicts may still exist it could already help :) Cheers, -- Pierre @pierrejoye | http://www.libgd.org -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
