Now the Blastwave “stable” freeze is over, there’s a further round of updates for my PHP4 packages which fix a few bugs and add a few new features. All available from http://www.blastwave.org/testing/ as usual.
This page may contain outdated information and/or broken links. It is included on this site in an effort to preserve historical information only.
Any testing would be greatly appreciated, as I really want these to be the final release, and to to get them out to the mirrors in the next week or so.
Changes in this release include the further modularisation - I have split the package into a core php4cgi (with added FastCGI support) , the Apache modules in mod_php, and the extensions in php4$extension.
To summarise :
If you only wanted the command-line interpreter, or CGI build, you’d just install php4_cgi. This includes the binaries, PEAR libraries, and various headers. It also takes care of installing a php.ini, if none exists. This is also the package you’d use if you wanted to set up a FastCGI environment, perhaps using iPlanet/SunOne/Java system webserver/whatever-sun-are-calling-it-this-month.
If you wanted to install a PHP module for Apache (either 1.x or 2.x), you’d install mod_php (which is the same package name as the one people currently download, e.g. CSWphp. ). This includes a dependency on php4_cgi, so if you install this, you’ll also get the PEAR libraries and “foundations” needed for PHP to function etc.
If you then want to add support for a particular extension, you install php4_$extension. For instance, to add MySQL support, you’d install php4_mysql. There is also a “bundle” package, which doesn’t contain any files, but does contain dependencies for php4_cgi, mod_php, apache 1.3.x, and all the extensions. This emulates the current monolithic build; for a full PHP4 installation, this is the package you’d install (pkg-get -i php4).
See my previous blog entries for details on the new build approach I am using.