since net-www/apache-2.0.52-r3 breaks almost anything, there're new ebuilds needed for every mod_*something*. Ok, most are adapted yet. But why is this ebuild unmasked, when the most important 3rd party apache module isn't migrated to the new layout yet? I updated apache w/o knowing the facts ("oh, an update is available"). After migrating all the configs, I see that mod_php isn't available for the new layout. Wow! We have so many PHP Webapps an portage, and mod_php isn't migrated yet, but net-www/apache-2.0.52-r3 is unmasked. Hmpf!!!! :-/ What now? Downgrade again? I need mod_php! I would like to see mod_php adapted to the new layout ASAP or net-www/apache-2.0.52-r3 should be masked again! Since it breaks your installation. mod_php is not one of the dozen little helper modules. It is *THE* most important add-on module for most of us. Reproducible: Always Steps to Reproduce:
*** This bug has been marked as a duplicate of 77556 ***
Note that it is still masked ~arch. If you're running ~arch then it's your responsibility to be extra careful about issues like this.
I run ~x86 to find and fix bugs. But ~arch doesn't mean, that the maintainer has no responsibility and that there's no need to be careful. Breaking your installation isn't an option for ~arch. For experiments you can mask your ebuilds. If you unmask, then you have to take care not to break anything you know about. And unmasking apache while mod_php isn't ported yet IS NOT NICE, because you know that you break anything that depends on PHP.
Please take the commentary to bug 77556.
