Jyri Very valid suggestion. Yes, we could simply deliver the mod_php5.so and /usr/apache2/ 2.2.4/conf.d/php5.conf within this new package. Any suggestions on a more appropriate package name ?
thanks sriram Jyri Virkki wrote: > Sriram Natarajan wrote: > >> I am hoping to address this issue with our next PHP integration and >> hence I am planning to integrate a separate package (say >> SUNWphp5-apache-module) that will deliver the following >> > > Funny, I was just looking at this ;-) > > I see in debian the equivalent package delivers, among other things: > > % dpkg -L libapache2-mod-php5 > ... > /etc/apache2/mods-available/php5.load > /etc/apache2/mods-available/php5.conf > ... > > % more /etc/apache2/mods-available/php5.conf > <IfModule mod_php5.c> > AddType application/x-httpd-php .php .phtml .php3 > AddType application/x-httpd-php-source .phps > </IfModule> > % more /etc/apache2/mods-available/php5.load > LoadModule php5_module /usr/lib/apache2/modules/libphp5.so > > > Since the 2.2.6 Apache package (available on internal pkg server, > unfortunately not externally yet) includes > Include /etc/apache2/2.2/conf.d/*.conf > we can probably do something similar (deliver the .so and suitable conf file). > > I'd really like to avoid any scripting in the package install due to, > as you say, the IPS (http://opensolaris.org/os/project/pkg/) future. > > >
