As requested via mail I tested the depend on dev-libs/localizer. The result is, that lighttpd does not need dev-libs/localizer at all. Even with "modlocalizer"-enabled it is not used. It seems, that modlocalizer-support was dropped some time. A "grep -Ri mod-localizer" in the sources showed, that the former --with-mod-localizer - option to configure is no more. It is the same issue with mod-cache and mod-chat (which always have been upcharge modules AFAIK). The output at the end of configure proofs that. Further the ebuild should depend on openldap with the ldap-USE-Flag. Additionally all options use the --with style (now). Last I noticed that mod_compress depends on bzip2, so this should be added to DEPEND: # ldd /usr/lib/lighttpd/mod_compress.so libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0xb7fcc000) [...] I am going to submit a patch to the current version, which reflects these changes I made. It seems to work well and the USE-Flags have now real uses ;-) Reproducible: Always Steps to Reproduce: 1. play around with the lighttpd-sources, ldd, ebuild and USE-Flags ;-)
Created attachment 51220 [details, diff] lighttpd-1.3.10-r1.ebuild.patch
mod-localizer, mod-cache and mod-chat are note distributed as part of lighttpd anymore. There is something like Apache's apxs in development to install these modules, but by now not production-ready, yet. Also the (unconditional) dependency >=dev-libs/localizer-0.3.3 does not make any sense (anymore?) and could be removed from lighttpd ebuild. Today the lighttpd-ebuild allways requires dev-libs/localizer - if you want to use mod-localizer (which actually does not work anyway), or not.
Fixed. I'd be very suprised if those enable_extension_enable calls *ever* worked, as all the lighttpd configure flags are --with-XXX, not --enable-XXX.
