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.
