| CARVIEW |
| DB_DataObject 1.9.4 (Mon, 21st Jun 10) |
| Date_Holidays_Spain 0.1.1 (Sun, 13th Jun 10) |
| Net_Sieve 1.2.2 (Sun, 13th Jun 10) |
| HTML_Template_Flexy 1.3.10 (Mon, 7th Jun 10) |
| Services_Twitter 0.6.1 (Sat, 5th Jun 10) |
 |
| HTML_Template_Flexy 1.3.10 (140.40) |
| Mail 1.2.0 (91.68) |
| DB_DataObject 1.9.4 (72.00) |
| HTML_Table 1.8.3 (35.58) |
| DB_DataObject 1.9.3 (23.06) |
| * downloads per day |
|
| Jesús Espino jespino |
| Simon Spencer silospen |
| Ryan Briscoe rbriscoe |
| See all |
PEAR - PHP Extension and Application Repository
» What is it?
PEAR is a framework and distribution system for reusable PHP components.
Sounds good? Perhaps you might want to know about installing PEAR on your system or installing pear packages.
You can find help using PEAR packages in the online manual and the FAQ.
If you have been told by other PEAR developers to sign up for a PEAR website account, you can use this interface.
» Hot off the Press
Google code channels work again
After the recent problems regarding the usage of PEAR channels hosted in google code SVN repositories, we are glad to announce that the problem has been fixed on both sides!
Reason for the problem was that PEAR sent HTTP “Host:” headers with the port included, i.e. “Host: pear.php.net:80″. This is completly valid according to the HTTP/1.0 specification, and it worked with all of the channels – except those from Google.
Google fixed their HTTP servers to accept Hosts with port numbers, and we at PEAR fixed the PEAR installer not to add the port to HTTP host headers. Version 1.9.1 of PEAR includes that fix.
PEAR channels on google code currently broken
PEAR channels hosted on google code (like the unofficial Smarty channel, unofficial Zend Framework channel and the unofficial Mediawiki channel) are currently broken.
The reason for it has been discovered in the corresponding bug report: HTTP requests containing a port number in the “Host” header field are rejected, returning a 404.
The issue is currently being investigated by Google. If you cannot wait, apply a hack-fix to your PEAR installation. Alternatively, use Pyrus, the next-gen PEAR installer.
PEAR in March 2010
After a quiet holiday season, the PEAR community has started rumbling again.
Digg gave PEAR a plug, new versions of Mail, Services_Facebook, System_Daemon, and HTML_Template_IT were released, the number of bugs reported dropped to less than one per package for a brief time, and two promising new proposals in PEPr arrived.
What’s even more exciting, we’ve got a continuous integration environment currently set up; discussion (and bug fixing) is turning more and more towards the future of pear, and the quiet on the mailing lists has vanished in a recent flood of posts.
Even better, we’ve seen the conceptual basis of PEAR (channel server and installer) take off with Pirum and PEARFarm being launched; and several large projects like PHPUnit, Smarty, and even Zend Framework (!) being installable via pear channels.
If this level of activity is anything to judge by, the future of PEAR looks bright for 2010!
PEAR Community
Need help?
You can find help and support on our mailing lists, and IRC channel
Our developers are also on LinkedIn, Ohloh, Twitter, Identi.ca or Facebook, as well as the wiki.