| 1 |
On 01/06/2016 02:36 PM, Sebastian Pipping wrote: |
| 2 |
> On 05.01.2016 20:35, Michael Orlitzky wrote: |
| 3 |
>> I just pushed a new revision with this fix. In eselect-php-0.8.2-r1, |
| 4 |
>> we ship both the new 70_mod_php.conf and the old 70_mod_php5.conf. The |
| 5 |
>> latter comes with a big warning at the top of it, stating that it is for |
| 6 |
>> backwards compatibility only. |
| 7 |
> |
| 8 |
> Cool, sounds like a great idea to me. |
| 9 |
> |
| 10 |
> I guess we don't need a news item any more then? |
| 11 |
> |
| 12 |
|
| 13 |
Upgraders still have a problem, but a much less severe one. After |
| 14 |
upgrading eselect-php, further attempts to `eselect php set apache2` |
| 15 |
will appear to have no effect, because the old 70_mod_php5.conf is |
| 16 |
loading the old symlink to libphp5.so. There are a few options: |
| 17 |
|
| 18 |
1. Leave things as is, and tell people what to do (read the elog) if |
| 19 |
they hit this situation. |
| 20 |
|
| 21 |
2. Proceed with a news item that basically says "read the elog." |
| 22 |
|
| 23 |
3. I could try to hack some magic into eselect-php to detect whether or |
| 24 |
not you have -DPHP5 set. Something simple, like grepping /etc/conf.d |
| 25 |
/apache2 for "PHP5". In that case we could omit a notice. |
| 26 |
This one simultaneously makes the most sense and feels like the |
| 27 |
biggest hack. |
Archives