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

+1 for 3.

You can remove the hack in a year or so. I think most important is a 
good user experience. If this requires a hack because the design of the 
tools give you no other choice than be it.


-- 
0x35A64134 - 8AAC 5F46 83B4 DB70 8317
             3723 296C 6CCA 35A6 4134