Hi
  I am hoping to integrate PHP 5.2.5 with Nevada build 86. PHP 5.2.5 is 
mostly a bug fix release. However, upgrading PHP in Nevada has become 
slightly complex  because of the current PHP package design. Current PHP 
packages include 'sub-minor' revision  information within its packages. 
For example, to upgrade from PHP 5.2.4 to PHP 5.2.5, we need to change 
all our php package name .  I believe that the decision to include the 
'sub-minor' version within the package name is only to address the 
perceived incompatibility concerns that we commonly have in Open Source 
projects. However, going by the change revision within every sub minor 
release, I don't see any major incompatibilities introduced between say 
PHP 5.2.4 and 5.2.5.  For more information , on PHP 5 change log, see - 
http://www.php.net/ChangeLog-5.php#5.2.5. 

 With nevada build 79, we integrated the following PHP packages - 
SUNWphp524root, SUNWphp524core , SUNWphp524usr, SUNWphp524doc, 
SUNWphp524man etc. Going forward, I would like to get every one's views 
on consolidating our packages to reflect something like

- Include only major and minor version in the package names and choose 
the package name to be more consistent with the rest of SFW 
consolidation.. For example, new php package could include only - 
SUNWphp52usr, SUNWphp52root and SUNWphp52doc. Consolidate SUNWphp524usr 
and SUNWphp524core into SUNWphp524usr.

- Deliver all third party PHP extensions like memcache, suhosin in its 
own package. This way, we can reduce the number of dependencies required 
to install PHP packages on Indiana . Please note that we already deliver 
MySQL and PostgreSQL extension in a separate package.

- Install php 5.2 series under /usr/php5/5.2 and under /etc/php5/5.2 
location. Appropriately, create a symbolic link for /usr/php5/5.2/bin to 
/usr/php5/bin so that sub directories like bin, lib etc can point to the 
latest version of PHP5


Any thoughts / concerns ?

Thanks
Sriram




Reply via email to