| 1 |
* Michael Orlitzky schrieb am 06.01.16 um 20:53 Uhr: |
| 2 |
> On 01/06/2016 02:36 PM, Sebastian Pipping wrote: |
| 3 |
> > On 05.01.2016 20:35, Michael Orlitzky wrote: |
| 4 |
> >> I just pushed a new revision with this fix. In eselect-php-0.8.2-r1, |
| 5 |
> >> we ship both the new 70_mod_php.conf and the old 70_mod_php5.conf. The |
| 6 |
> >> latter comes with a big warning at the top of it, stating that it is for |
| 7 |
> >> backwards compatibility only. |
| 8 |
> > |
| 9 |
> > Cool, sounds like a great idea to me. |
| 10 |
> > |
| 11 |
> > I guess we don't need a news item any more then? |
| 12 |
> > |
| 13 |
> |
| 14 |
> Upgraders still have a problem, but a much less severe one. After |
| 15 |
> upgrading eselect-php, further attempts to `eselect php set apache2` |
| 16 |
> will appear to have no effect, because the old 70_mod_php5.conf is |
| 17 |
> loading the old symlink to libphp5.so. There are a few options: |
| 18 |
> |
| 19 |
> 1. Leave things as is, and tell people what to do (read the elog) if |
| 20 |
> they hit this situation. |
| 21 |
> |
| 22 |
> 2. Proceed with a news item that basically says "read the elog." |
| 23 |
> |
| 24 |
> 3. I could try to hack some magic into eselect-php to detect whether or |
| 25 |
> not you have -DPHP5 set. Something simple, like grepping /etc/conf.d |
| 26 |
> /apache2 for "PHP5". In that case we could omit a notice. |
| 27 |
> This one simultaneously makes the most sense and feels like the |
| 28 |
> biggest hack. |
| 29 |
|
| 30 |
+1 for 3. |
| 31 |
|
| 32 |
You can remove the hack in a year or so. I think most important is a |
| 33 |
good user experience. If this requires a hack because the design of the |
| 34 |
tools give you no other choice than be it. |
| 35 |
|
| 36 |
|
| 37 |
-- |
| 38 |
0x35A64134 - 8AAC 5F46 83B4 DB70 8317 |
| 39 |
3723 296C 6CCA 35A6 4134 |
Archives