>>> But watch out -- after the eselect, you'll need to move your php.ini >>> from e.g. /etc/php/apache2 to /etc/php/apache2-php5.3. >> >> Here I get confused. I believe a "development version" of php.ini was >> installed to /etc/php/apache2-php5.3/php.ini. It included a >> development value for error_reporting which I needed to change to the >> production value in order to prevent squirrelmail from triggering many >> error messages. At this point I have my old php.ini (which I don't >> think I ever edited) and the new development version of php.ini for >> 5.3.4. I did a diff between them and there are about 15 chunks of >> difference. The problem is I'm not sure which changes are due to the >> 5.3.3->5.3.4 switch and which are due to the fact that it's a >> development version of the config file. What I'd like to do is run a >> default 5.3.4 production php.ini but I don't know how to come up with >> that. > > New/deleted parameters are probably from the upgrade. Values that have > been changes are probably your changes. You can re-emerge PHP with the > production php.ini according to this (I haven't tried it): > > http://olemarkus.org/2010/10/choosing-between-development-and-production-version-of-php-ini/
Ah, perfect! Adding the following to /etc/make.conf and re-emerging php I was able to use etc-update to merge the latest production version of php.ini: PHP_INI_VERSION="production" I guess we're in a transitional phase with PHP on Gentoo. I hope it works out. - Grant >> What is gained by this new extra layer for PHP on Gentoo? I was happy >> when it behaved like every other ebuild and I could use etc-update >> along with -5 and I didn't have to bother with eselect. > > A ton of crap broke with the PHP 5.2 -> 5.3 upgrade. In theory, this > will help with future upgrades; but I'm not sure how, since I can't > *run* both versions at the same time. Does anyone know how having 5.3 > installed will help me when I'm stuck running 5.2 for some of my sites?
