Hi I am currently working towards PHP 5.2.6 integration and as part of this work I am working towards refactoring our PHP package to make it simpler and easier to maintain. The reasoning being that micro releases within PHP tend to retain backward compatibility and hence we would like to remove the 'micro' release version information within our package names and file layout. At the same time, we do want to the ability to carry multiple versions (either minor or major releases) . For example, customers using OpenSolaris should still be able to install PHP 5.2.x and PHP 5.3.x concurrently.
Considering that PHP file layout allows <version> names within , we can easily coexist PHP binaries and libraries with multiple versions. However, Apache / PHP glue packages need to be updated to have support for co-existence as well. Currently, this issue is not very well addressed and I would like to explore the possibility of addressing this issue with this integration. As part of Apache / PHP glue, currently we deliver the following to our customers /usr/apache/2.2/libexec/mod_php5.so -> PHP 5.2.x core runtime (apache module) /etc/apache/2.2/conf.d/php5.ini - INI file that gets read by Apache startup and loads PHP5 module Though, it is possible to ship multiple versions of PHP core apache module, it does not much make sense to deliver multiple versions of PHP ini file (configuration information for apache) . So, I think I have 2 options - roll in the Apache / PHP glue module (mod_php5.so) within SUNWphp52 package (no need for SUNWapch22m-php5 package) and deliver the apache / php module under /usr/php5/<major>.<minor>/libexec/mod_php5.so and create an appropriate symbolic link at /usr/apache2/2.2/libexec/mod_php5.so . Also, always deliver a single PHP INI file (SUNWapch22r-php5) which will load the mod_php5.so that is symbolic linked to /usr/apache/2.2/libexec/mod_php5.so - Continue delivering PHP version specific Apache / PHP glue packages (like SUNWapch22m-php52 and SUNWapch22r-php52). It is user's responsibility to avoid having ending up with multiple PHP ini files under /etc/apache2/2.2/conf.d directory. What do you guys think ? Or is there a better way to address this ? Your comments / thoughts on these will be much much appreciated. thanks sriram
