The ebuild's src_configure() function contains the line "$(use_enable curl mlogc)" so it appears that building mlogc requires the curl use flag, but it is never installed. Running: USE="curl" emerge www-apache/mod_security grep mlogc /var/db/pkg/www-apache/mod_security-2.7.7/CONTENTS grep shows no results. Running: USE="curl" ebuild /usr/portage/www-apache/mod_security/mod_security-2.7.7.ebuild compile find /var/tmp/portage/www-apache/mod_security-2.7.7 -name mlogc -type f -executable find returns /var/tmp/portage/www-apache/mod_security-2.7.7/work/modsecurity-apache_2.7.7/mlogc/mlogc I'm guessing src_install() needs to have some more code added to handle mlogc based on the curl use flag.
Hi Chris, the awesome piece of software lacks a maintainer currently... Would you like to proxy maintain it?
Testing an overlay with the following added to src_install(): if use curl; then exeinto /usr/bin doexe "${S}/mlogc/mlogc" dodir /etc/apache2 mv "${S}/mlogc/mlogc-default.conf" "${D}/etc/apache2/mlogc.conf" fi I wouldn't mind being a proxy maintainer for this, my only hesitation would be my available free time can be unpredictable.
Created attachment 448042 [details] mod_security-2.7.7-r1.ebuild Attached ebuild with mlogc install working.
CCing proxy-maintainers
I just committed mod_security-2.9.1 to fix this. Thanks for the report and the suggested fix. I changed the USE flag name to "mlogc", because USE=curl was kind of obtuse, and the configuration file is installed straight to /etc/mlogc.conf. Oh and the log-collector perl thingy is installed too. I don't use any of this stuff, so please report back if I screwed up in some way =)
