The exim-4.04-r1 ebuild has use flags that enable the LOOKUP_LDAP & LOOKUP_MYSQL modules. My virtual host exim config uses LOOKUP_DSEARCH. It would be nice if there was a use flag for LOOKUP_DSEARCH (and the rest of the LOOKUP_* modules, I suppose). Chris.
Added support for LOOKUP_DSEARCH to the ebuild. This will not be activated via a use variable as it is a useful function to have regardless of system configuration. emerge rsync emerge exim I will check and see if there are any other relevant LOOKUP variables over the next day or two. Upon finishing the LOOKUP changes I will release a -r2 and close the bug report.
added LOOKUP_CDB ... more coming :)
Many changes have been made to the exim ebuild. Can you please look over the ebuild and tell me if you notice anything missing? exim-4.05 will be released into portage soon after the portage freeze is lifted.
I've verified that the 4.04-r2 ebuild fixes the bug okay. Thanks. If you want me to test the 4.05 ebuild, then you'll have to add it to the portage tree (perhaps masked), so that I can see it. I don't use CVS. Chris.
I have added exim-4.05 to portage. It is currently masked in profiles/package.mask Let me know how it works for you!
I've verified that exim-4.05 works too. Chris.
lookups have been changed from mta-* to mysql, ssl, mysql, and pgsql to match with system default use variables. Thanks for testing the lookup support.
