pear php

PEAR Development on Github - Official Blog of the PEAR Group/PEA...

Planet PHP  Sat, 11/05/2011 - 18:52

Like many other projects, many components of PEAR have started a migration to github.

We have two primary organisations set up for PEAR and PEAR2.

While the existing PEAR packages will continue to use the pear.php.net distribution and bug tracking capabilities; it’s never been easier to contribute to a PEAR package – simply fork; add your changes and send us a pull request.


 

PHP with Intl and Gettext on OSX Lion - Bertrand Mansion

Planet PHP  Sat, 08/06/2011 - 13:23

Mac OSX Lion ships with PHP 5.3.6. There are also other ways to get PHP working on Lion, for example:


 

PHP Components: Shipping Documentation With Your Component - Stu...

Planet PHP  Thu, 04/28/2011 - 01:00

In my Beyond Frameworks talk, I explained how a component-based architecture can help answer some of the important (i.e. expensive!) questions you might face when creating long-lived apps that rely on a PHP framework.

In this series of blog posts, I’m going to look at how to go about creating and working with components.


 

Creating A Skeleton Component - Stuart Herbert

Planet PHP  Thu, 03/24/2011 - 00:00

In my Beyond Frameworks talk, I explained how a component-based architecture can help answer some o


 

PHPUnit 3.5 Upgrading Woes - Sebastian Bergmann

Planet PHP  Fri, 10/22/2010 - 02:30

The issues related to upgrading from a previous version to PHPUnit 3.5 that I mentioned in the release announcement are more serious than I initially thought.

Only today did I find the time to really investigate the root cause.

Here is the situation before the upgrade:


 

Google code channels work again - Official Blog of the PEAR Grou...

Planet PHP  Sat, 05/29/2010 - 00:35

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.


 

PEAR Blog: Fixing "unsupported protocol"

PHPDeveloper.org  Fri, 08/28/2009 - 06:55

If you've had issues with an "unsupported protocol" message when working with the PEAR installation on your PHP instance, you should check out this quick post from the PEAR blog with a tip on how to fix it.


 

PEAR Blog: The elections are still going!

PHPDeveloper.org  Mon, 08/03/2009 - 08:45

The PEAR blog has a quick note about this year's elections - specifically that they have been extended due to some communication issues.


 

The PEAR Blog: pear.php.net moving on

PHPDeveloper.org  Tue, 06/16/2009 - 06:53

As is mentioned on the PEAR blog today, there's some new advancements that are being made to make submitting proposals simpler.