On 01/04/2016 02:27 PM, Michael Orlitzky wrote:
>
> I may be able to fix that by simply including the old 70_mod_php5.conf
> for backwards compatibility.
>
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.
The way this should work for upgraders is:
* You currently have php-5.x eselected, -DPHP5 defined, and a symlink
to libphp5.so in your apache2 modules directory.
* You upgrade eselect-php.
* The way we handle the module symlink and conf.d definition has
changed, but the new eselect won't touch your old libphp5.so
symlink, and you still have -DPHP5 defined.
* With 70_mod_php5.conf still around, everything keeps working
exactly as it did before the eselect-php upgrade.
* If you try to use `eselect php ... apache2`, it will create a NEW
symlink, under the new scheme. Nothing else happens. Hopefully
this convinces you to read the elog or apache config.
* If you define both -DPHP5 and -DPHP, you can get problems. Don't do
that?
* If you switch from -DPHP5 to -DPHP, the new 70_mod_php.conf kicks
in, and the new scheme gets used, and your eselect choice will
start working. Now you can delete 70_mod_php5.conf.
tl;dr it should keep working until you try to eselect and "it doesn't do
anything." Then hopefully you try to figure out why and realize you need
to update to -DPHP. But until then your current PHP keeps running.
If you had trouble with the upgrade, first of all -- sorry, and could
you please give the new revision a try? This upgrade should only be
annoying, not fatal.
