I would rather not delete that file myself without review from your side.
To my understanding, it is unused and can be deleted.
# fgrep -Rl '70_mod_php5.conf-apache2' .
The reason why I would like to have it removed is the use of AddHandler:
# fgrep -R AddHandler .
./files/70_mod_php5.conf-apache2: AddHandler application/x-httpd-php .php .php5 .phtml
./files/70_mod_php5.conf-apache2: AddHandler application/x-httpd-php-source .phps
Please see bug #538822 for why that is a problem.
I just found that my call to grep was the problem. The file is actually still used:
# fgrep -Rl 70_mod_php5 . | fgrep ebuild | sort
So a fix is needed rather than removal. Please see bug #538822 for a proposed fixed.
I intend to fix this myself with the same fix as used for eselect-php in bug #538822.
Please object now, if you would like to take over. Thanks.
Update once again: File files/70_mod_php5.conf-apache2 is NOT used by the ebuilds.
The previous grep matches on "70_mod_php5" are all like
# fgrep -A1 70_mod_php5 *.ebuild
and apache-module_pkg_postinst only prints information.
# fgrep -Rl -- -apache2 .
and a look at the change log reveals that there was a -r1 of that file at some point
which fixed the AddHandler part, interestingly.
+ 05 Apr 2015; Sebastian Pipping <firstname.lastname@example.org> php-5.3.29.ebuild,
+ php-5.4.36.ebuild, php-5.4.37.ebuild, php-5.4.38.ebuild, php-5.4.39.ebuild,
+ php-5.5.20.ebuild, php-5.5.21.ebuild, php-5.5.22.ebuild, php-5.5.23.ebuild,
+ php-5.6.4.ebuild, php-5.6.5.ebuild, php-5.6.6.ebuild, php-5.6.7.ebuild,
+ Resolve unused and misleading files/70_mod_php5.conf-apache2, add note about
+ /etc/apache2/modules.d/70_mod_php5.conf actually being provided by
+ app-eselect/eselect-php by now (bug #544564)