| 1 |
On 01/07/2016 07:52 PM, Marc Schiffbauer wrote: |
| 2 |
>> |
| 3 |
>> 3. I could try to hack some magic into eselect-php to detect whether or |
| 4 |
>> not you have -DPHP5 set. Something simple, like grepping /etc/conf.d |
| 5 |
>> /apache2 for "PHP5". In that case we could omit a notice. |
| 6 |
>> This one simultaneously makes the most sense and feels like the |
| 7 |
>> biggest hack. |
| 8 |
> |
| 9 |
> +1 for 3. |
| 10 |
> |
| 11 |
> You can remove the hack in a year or so. I think most important is a |
| 12 |
> good user experience. If this requires a hack because the design of the |
| 13 |
> tools give you no other choice than be it. |
| 14 |
> |
| 15 |
|
| 16 |
Done in recent eselect-php: |
| 17 |
|
| 18 |
$ sudo eselect php set apache2 1 |
| 19 |
!!! Warning: The apache2 configuration has changed in this |
| 20 |
!!! Warning: version of eselect-php. You should define "-D PHP" |
| 21 |
!!! Warning: and not "-D PHP5" for apache. The module is now |
| 22 |
!!! Warning: loaded by 70_mod_php.conf (was 70_mod_php5.conf). |
| 23 |
!!! Warning: After you have changed "-D PHP5" to "-D PHP", |
| 24 |
!!! Warning: you should remove 70_mod_php5.conf to eliminate |
| 25 |
!!! Warning: this warning. Until you have done so, your eselect |
| 26 |
!!! Warning: choices for apache2 will have no effect. |
| 27 |
|
| 28 |
Please restart apache for the changes to take effect. |
| 29 |
|
| 30 |
Users may get that warning more than once if we reinstall |
| 31 |
70_mod_php5.conf, but it's harmless and less hacky than grepping |
| 32 |
/etc/conf.d/apache2. |
| 33 |
|
| 34 |
I think we can forego the news item? Thanks for the suggestions. |
Archives