Gentoo's Apache configuration appears to be broken.

I recently ran into a problem using the mod_perl Apache::Test module.
Apache::Test uses /usr/sbin/apxs -q LIBEXECDIR to locate libperl.so. Which
when executed returns /usr/lib/apache. However, someone doing Apache ebuilds
decided to create a second module directory for non Apache core modules
called /usr/lib/apache-extramodules. Which is where Gentoo currently
installs libperl.so. Thus breaking Apache::Test's ability to use apxs to
locate it. 

Both of these module locations are symbolically linked to appear in
/etc/apache as: 

extramodules -> ../../usr/lib/apache-extramodules 
modules -> ../../usr/lib/apache 

So the multitude of mod_php, mod_perl, mod_throttle, etc. modules all appear
to be installed in a location (extramodules) which apxs can't locate and
work with at runtime. Which I believe is kind of the whole purpose of apxs
right? 

I traded emails with Stas Beckman (mod_perl guru and author of "Practical
mod_perl" and Apache::Test). It is his opinion
(http://www.mail-archive.com/modperl@apache.org/msg35963.html) if I'm
reading it right that there should be only one LIBEXECDIR so that apxs -q
LIBEXECDIR can report correct values. I supplied him with a patch, but it is
his opinion Gentoo is broken... and that special casing things for Gentoo
would do more evil than good.

There are a sizable number of mod_* modules which would need to be fixed. To
create a list of the 59 files which currently mention extramodules I used: 

find /usr/portage|xargs grep "extramodules"|perl -pe 's/:.*//'|sort|uniq 

Note: a sizeable number of those refer to ebuilds with multiple revisions. 

Does anyone know why extramodules exists? I.e. what justifies a non-standard
apache install which breaks runtime apxs support?

--
Garrett Goebel
IS Development Specialist

ScriptPro                   Direct: 913.403.5261
5828 Reeds Road               Main: 913.384.1008
Mission, KS 66202              Fax: 913.384.2180
www.scriptpro.com          garrett at scriptpro dot com