Hi! It's rather easy to overlook the change from -DPHP5 to -DPHP. I will save you the details of how hard this bit me today. I would like to suggest to make the current situation more user friendly. In particular, I would like to suggest * a portage news entry and * considering a temporary backwards compatibility layer. For the latter, I could imagine that something like <IfDefine PHP5> Define PHP </IfDefine> on top could work. If putting >=app-eselect/eselect-php-0.8.1 into package.mask again, that's what I would suggest to do first to win some time. What do you think? Thanks and best, Sebastian
- putting [..] into package.mask again + putting [..] into package.mask again is an option
(In reply to Sebastian Pipping from comment #0) > > For the latter, I could imagine that something like > > <IfDefine PHP5> > Define PHP > </IfDefine> > This is apache-2.4 only unfortunately. I tried a similar approach but using a custom Error <https://httpd.apache.org/docs/2.4/mod/core.html#error> message to tell the users what do to. Same problem.
I would vote for a news item.
News item posted for review to gentoo-dev: http://thread.gmane.org/gmane.linux.gentoo.devel/99222
I've done a bunch of work on eselect-php that (hopefully) mitigates this entirely. Your existing 70_mod_php5.conf was never supposed to go away. Now we ship it (in addition to the new 70_mod_php.conf) for backwards-compatibility. And in eselect-php-0.8.5, the user gets a warning when he tries to change his apache target unless he's updated his configuration: $ sudo eselect php set apache2 1 !!! Warning: The apache2 configuration has changed in this !!! Warning: version of eselect-php. You should define "-D PHP" !!! Warning: and not "-D PHP5" for apache. The module is now !!! Warning: loaded by 70_mod_php.conf (was 70_mod_php5.conf). !!! Warning: After you have changed "-D PHP5" to "-D PHP", !!! Warning: you should remove 70_mod_php5.conf to eliminate !!! Warning: this warning. Until you have done so, your eselect !!! Warning: choices for apache2 will have no effect. Please restart apache for the changes to take effect. Combined, those two changes should prevent breakage on upgrades and surprises for anyone who skips the elog message.
Thank you!
