| 1 |
On 01/04/2016 12:49 PM, Rich Freeman wrote: |
| 2 |
> |
| 3 |
> My understanding (which could be wrong) is that this update will break |
| 4 |
> things even if the user never runs eselect php afterwards. I can't |
| 5 |
> tell you the last time I touched the php eselect module, because major |
| 6 |
> updates to php are rare. |
| 7 |
> |
| 8 |
|
| 9 |
I was going to say "no, everything should keep working" but I decided to |
| 10 |
test a fresh upgrade before sticking my foot in my mouth. Now I know |
| 11 |
what people are complaining about. |
| 12 |
|
| 13 |
If you've never touched 70_mod_php5.conf, portage will remove it when |
| 14 |
you upgrade eselect-php. That does break an existing installation until |
| 15 |
you've run `eselect php...` and munged -DPHP5 to -DPHP. What I intended |
| 16 |
was for 70_mod_php5.conf to stick around until you've had a chance to |
| 17 |
deal with the configuration change. In that case everything keeps |
| 18 |
working until after you've run eselect. |
| 19 |
|
| 20 |
I may be able to fix that by simply including the old 70_mod_php5.conf |
| 21 |
for backwards compatibility. |
Archives