1 |
>> Thank you, that fixed it. I'm getting some errors in squirrelmail but |
2 |
>> functionality seems to be intact. |
3 |
>> |
4 |
>> Since things seem to be working with php-5.3.4, how can I get rid of |
5 |
>> the older version of php that must be installed in another slot? I'm |
6 |
>> hoping that simplifies things a bit. PHP on Gentoo just got more |
7 |
>> complicated and all I need out of it is squirrelmail. Actually, I |
8 |
>> wish there was a decent webmail client that didn't depend on PHP at |
9 |
>> all so I could remove it. |
10 |
>> |
11 |
>> - Grant |
12 |
>> |
13 |
> |
14 |
> The slotting is just for major versions, so you probably don't have two |
15 |
> installed (you most likely went from 5.3.3 to 5.3.4). |
16 |
|
17 |
You're right. |
18 |
|
19 |
> But watch out -- after the eselect, you'll need to move your php.ini |
20 |
> from e.g. /etc/php/apache2 to /etc/php/apache2-php5.3. |
21 |
|
22 |
Here I get confused. I believe a "development version" of php.ini was |
23 |
installed to /etc/php/apache2-php5.3/php.ini. It included a |
24 |
development value for error_reporting which I needed to change to the |
25 |
production value in order to prevent squirrelmail from triggering many |
26 |
error messages. At this point I have my old php.ini (which I don't |
27 |
think I ever edited) and the new development version of php.ini for |
28 |
5.3.4. I did a diff between them and there are about 15 chunks of |
29 |
difference. The problem is I'm not sure which changes are due to the |
30 |
5.3.3->5.3.4 switch and which are due to the fact that it's a |
31 |
development version of the config file. What I'd like to do is run a |
32 |
default 5.3.4 production php.ini but I don't know how to come up with |
33 |
that. |
34 |
|
35 |
What is gained by this new extra layer for PHP on Gentoo? I was happy |
36 |
when it behaved like every other ebuild and I could use etc-update |
37 |
along with -5 and I didn't have to bother with eselect. |
38 |
|
39 |
- Grant |