This stuff is in the works. The current pear tool only works with php-based pear packages, but it will soon get a wrapper that will phpize and build extensions for you with proper dependency checking.
Here is a current snapshop of what works. (I don't think the pear guys are doing a great job of advertising their progress, which is part of this problem) % pear remote-list Available packages: =================== +----------------------+---------+ | Package | Version | | Archive_Tar | 0.4 | | Auth | 1.0.1 | | Auth_HTTP | 1.0 | | Benchmark | 1.1 | | Cache | 1.4 | | Crypt_CBC | 0.3 | | Crypt_Rc4 | 0.1 | | Date | 1.1 | | DB | 1.2 | | DB_Pager | 0.7 | | File | 1.0.1 | | File_Find | 0.1 | | File_SearchReplace | 1.0 | | HTML_QuickForm | 2.1 | | HTTP | 1.1 | | HTTP_Request | 1.0 | | HTTP_Upload | 0.8 | | Log | 1.1 | | Mail_Mime | 1.1 | | Net_CheckIP | 1.0 | | Package | Version | | Net_Curl | 0.1 | | Net_Dig | 0.1 | | Net_Geo | 1.0 | | Net_NNTP | 0.1 | | Net_Ping | 1.0 | | Net_POP3 | 1.1 | | Net_Portscan | 1.0.1 | | Net_Socket | 1.0.1 | | Net_URL | 1.0.1 | | Net_UserAgent_Detect | 1.0 | | Numbers_Roman | 0.1 | | Pager | 1.0 | | Payment_Clieop | 0.1 | | PEAR | 0.9 | | Science_Chemistry | 1.0.2 | | XML_CSSML | 1.1 | | XML_Parser | 1.0 | | XML_RPC | 1.0.3 | | XML_RSS | 0.9.1 | | XML_Transformer | 0.3 | | Package | Version | | XML_Tree | 1.1 | +----------------------+---------+ % pear list Installed packages: =================== +----------------+---------+--------+ | Package | Version | State | | Archive_Tar | 0.4 | stable | | Console_Getopt | 0.10 | beta | | DB | 1.2 | stable | | XML_Parser | 1.0 | stable | | XML_RPC | 1.0.3 | stable | | Net_URL | 1.0.1 | stable | | Payment_Clieop | 0.1 | stable | | XML_Tree | 1.1 | stable | | File | 1.0.1 | stable | | File_Find | 0.1 | stable | +----------------+---------+--------+ % pear list-upgrades Available Upgrades (stable): ============================ +---------+---------+------+ | Package | Version | Size | +---------+---------+------+ % pear install Net_Portscan install ok: Net_Portscan 1.0.1 % pear list Net_Portscan Installed Files For Net_Portscan ================================ +------+------------------------------------------------------------+ | Type | Install Path | | php | /usr/local/lib/php/Net/Portscan.php | | doc | /usr/local/share/php/doc/pear/Net_Portscan/README.portscan | | php | /usr/local/lib/php/Net/tests/01-portscan.php | +------+------------------------------------------------------------+ % pear config-show Configuration: ============== bin_dir /usr/local/bin doc_dir /usr/local/share/php/doc/pear ext_dir /usr/local/lib/php/extensions/debug-non-zts-20010901 http_proxy <not set> master_server pear.php.net password <not set> php_dir /usr/local/lib/php preferred_state stable umask 022 username <not set> verbose 1 > My idea was something like the following: (From php4/) > ./pecl-list <-- This would give a list and short description of all > extensions in PECL > ./pecl-download FooBar <-- This would download FooBar and put it in ext/ > and run ./buildconf > Then the user could just run ./configure and configure with the downloaded > extension. Most users still prefer to statically build their extensions and > not use phpize although that could be optional. > > Once we have this kind of mechanism I think it'll be much easier for us to > move non-core extensions into PECL. As I mentioned before I still think > that the traditional core extensions should stay in the main PHP > distribution. PHP in embedded systems is rare and it's no excuse to remove > core extensions from PHP. People who want to build a naked PHP for embedded > systems can ./configure PHP accordingly! > > My 2 cents. > > Andi > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
