Arvind Arvind Srinivasan wrote: > Sriram Natarajan wrote: >> Hi >> I would like to integrate PEAR/PECL support within PHP in Open >> Solaris. Here with, I would like to address the following bugs. I am >> hoping to address these issues for Nevada build 85. Can you kindly >> take a look at this web rev report and let me know , at your earliest >> convenience, if you see any issues >> >> Web Rev: http://cr.opensolaris.org/~sn123202/fixes_for_b85.2/webrev/ >> >> 6625633 <http://monaco.sfbay.sun.com/detail.jsp?cr=6625633> php5 >> integration needs to support PEAR / PECL extension >> 6668699 <http://monaco.sfbay.sun.com/detail.jsp?cr=6668699> php could >> enable dtrace extension by default >> 6669474 <http://monaco.sfbay.sun.com/detail.jsp?cr=6669474> compile >> runtime libraries are included in php modules (again) >> >> > --- old/usr/src/cmd/php5/Makefile.sfw Fri Feb 29 00:55:17 2008 > +++ new/usr/src/cmd/php5/Makefile.sfw Fri Feb 29 00:55:17 2008 > > + PHP_PEAR_TEMP_DIR=/tmp/pear/temp \ > + PHP_PEAR_CACHE_DIR=/tmp/pear/cache \ > + PHP_PEAR_DOWNLOAD_DIR=/tmp/pear/cache \ > > What are these used for? Are they used at build time or at run time? > Should they point inside /tmp or /var/tmp? > Thanks for the review. PEAR uses these definition during build time to appropriately create the /etc/php5/5.2.4/pear.conf with these values. Without these definitions, default pear.conf is created which is very build and host specific. Please note that PEAR_TEMP_DIR and PEAR_CACHE_DIR is for temporary purposes only. We don't need the content in these directory after reboot. On Solaris, /tmp/ is not retained over reboot. Hence, chose this location over /var/tmp.
thanks sriram
