On 01/04/2016 08:40 AM, Michał Górny wrote: > > Therefore, I think you should really work on some kind of backwards > compatibility for people using '-D PHP5' that would prevent those kind > of issues at least for some migration period. With big fat warnings for > people who run it. >
I wasn't able to come up with something that worked on apache-2.2 and was backwards-compatible or failed "off." The apache module name for PHP changed with php-7.0. This forces a big change in 70_mod_php.conf, and a corresponding change in eselect-php (which must be run once before anything will work). The problem is to come up with an apache-2.2 config that works for new 5.6 users, 5.6 -> 7.0 eselect switchers, and new 7.0 users. Someone always gets screwed. If anyone has a concrete idea that works better, it's not too late to change it.
