Re: Re: cvs: pecl /paradox CREDITS EXPERIMENTAL config.m4 paradox.c php_paradox.h

Perhaps the PEAR installer should create a command named "pecl" as well as "pear." All of the commands would be available to pecl, but it would work on only pecl packages, and not pear. In windows, this would be pecl.bat, obviously. This would be the simplest solution. Then, pear remote-list would only list remote php packages, and pear list would only list local php packages. pecl remote-list would only list remote pecl packages, etc. etc. To implement this, there would need to be an additional hidden option for the pear command, perhaps --__pecl, which would not show up in the list of commands, and would automatically be passed by the "pecl" command-line. For the Web Installer, there could be 2 tabs at the top of the page, PEAR and PECL. I haven't got a working install of php-gtk, so I can't comment on the gtk installer. I also agree 100% that this list is no place to discuss C of any kind. Regards, Greg Tomas V.V.Cox wrote:

On Thursday, July 24, 2003 11:19, Wez Furlong wrote:

Hmm, I don't think that many of the people on pear-dev are really qualified to make such a decision about a C module, so if it should have been discussed anywhere, it should have been discussed on the internals list.

IMHO the addition/discussion of Pecl extensions should be done by the php group or at least by the main php dev and should ocurr on the internals list. In the next time we should start thinking on how to clearly difference C and PHP packages at the web. Ideas are welcome :-)