Since apache 2.4.6, mod_macro seems to be included in the apache package itself. There is no use flag available to enable/disable mod_macro and it currently conflicts if mod_macro is installed.
Steps to Reproduce:
1. emerge mod_macro
2. emerge apache
* Detected file collision(s):
apache 2.4.6 blocks mod_macro and includes a use flag to enable/disable.
Created attachment 353836 [details, diff]
Fixes macro as a apache built-in module and blocks mod_macro external package.
What still needs to be done:
Add mod_macro config file and example in gentoo-apache and enable including them in the ebuild.
Reassigning to current apache maintainer, conflict confirmed.
*** Bug 521342 has been marked as a duplicate of this bug. ***
*** Bug 535840 has been marked as a duplicate of this bug. ***
Looks like current ebuild sets RDEPEND/DEPEND at eclass level (also affecting to 2.2) :S
If anyone could provide a patch for current ebuild and eclass, it would for sure help to get this finally solved
Wouldn't it be enough to add a block to apache-2.eclass?
Currently we have:
case $(get_version_component_range 1-2) in
How about to add and RDEPEND line to all 2.4
+ 07 Jun 2015; Pacho Ramos <firstname.lastname@example.org> -apache-2.4.12.ebuild,
+ apache-2.4.12-r1.ebuild, metadata.xml:
+ mod_macro is now provided by apache itself (#477702 by Jan Vansteenkiste, and
+ Tomas Mozes)