On 9 Jul 2008, at 04:02, Sriram Natarajan wrote: > 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.
Yep, but only (IMHO) if the user explicitly asks for it. Would a good solution be for the package manager to prompt the user "You seem to have another version (5.2.x) installed. Shall I remove that now?" > - 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 You mean, supply an ApacheXX-phpYY package that's just the symlink, or drop it altogether? > - 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. Surely no package should ever overwrite an existing config file! If that's the user's responsibility, what happens to users who don't realise it until too late? > What do you guys think ? Or is there a better way to address this ? > Your comments / thoughts on these will be much much appreciated. Why is there any question of multiple php.ini files? Does it differ between PHP versions? If so, maybe php.ini could be a symlink too. -- Nick Kew
