Install PHP 5.2 on Red Hat Enterprise Linux 5.6
Red Hat Enterprise Linux 5.6 ships with PHP 5.1, and also makes PHP 5.3 available. PHP 5.1 is the default, and the server will never update from 5.1 to 5.3 without being explicitly configured to do so. But you may notice that glaring hole where PHP 5.2 should be. Where does that leave users of several popular PHP-based Content Management Systems? There are a few officially supported releases and myriad plugins and extensions that require PHP 5.2.
The CentOS Testing repository comes to the rescue (CentOS provides a lot of very helpful repositories). They even have a HowTo PHP5.1 to 5.2 page. The problem with this page is that it includes some terribly inconvenient styling. A quick cut and paste yields a config page that carries indentation. Yum will fail to parse your configuration data if it is preceded by a space (or if a comment is preceded by space).
If you attempted to follow the wiki instructions, but instead found yourself staring at a “Config Error: File contains no section headers.” message, check the current CentOS-Testing.repo file on the CentOS/5 server. Notice the absence of any indentation preceding the repository section header, variables, and comments. Either use this version in /etc/yum.repos.d/CentOS-Testing.repo (just make sure you add an “includepkgs=php*” at the bottom!!!), or manually remove the indentation from the CentOS wiki version. After that, a simple “yum update” or “yum update php*” will update your server with PHP 5.2. Apache users need to restart apache with “/sbin/service apache restart” (or your preferred apache restarting technique), and PHP 5.2 is up and running on your web server.
2 Responses to “Install PHP 5.2 on Red Hat Enterprise Linux 5.6”
Leave a Reply
When optimizing my site for search engines, I know to put the title tags in the header, only use one title tag per page, and ma...
What Our Clients Are Saying
We have worked with Accella for three years now. What i enjoy the most is the accessibility of their staff, from their PM to their account reps...They stand behind their work. After the product is delivered, they have stuck around to make sure the product works correctly in our environment and they have stuck around for any fallout during end user testing.