As of apache-2.0.52-r3 and -1.3.33-r1 apache uses new paths and configurations. We have created eclasses to make apache module maintainers life's easier. See http://dev.gentoo.org/~vericgar/doc/apache-package-refresh.html on how to update your ebuild to use the new eclass. When we unmask the new apache revision, skunkweb will break if it isn't adapted to the new eclass.
Our unmask date was pushed forward slightly and we're now hoping to unleash our stuff this saturday (26th). As we're running out of time, I've made an attempt at updating the skunkweb-3.4.0 ebuild to use the new apache-module eclass which I'll attach in a sec. This ebuild always builds mod_skunkweb, but it must be enabled in /etc/conf.d/apache{,2} for it to actually be loaded by Apache. I've also tweaked the config to reflect this (it will now need to be bundled in the tree, too). Attachments to follow, critique saught. :)
Created attachment 52043 [details] Updated ebuild
Created attachment 52044 [details] Updated config file
*remind* *remind* please verify'n'commit beu's updated ebuild. This bug depends on apache to be unmasked (that can't wait just yet another decade)
done some tests: in cvs. _very_ good work with the eclass...