Summary: | maildrop with ldap should not automatically use config | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin von Gagern <Martin.vGagern> |
Component: | Current packages | Assignee: | Net-Mail Packages <net-mail+disabled> |
Status: | RESOLVED WONTFIX | ||
Severity: | minor | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin von Gagern
2005-03-03 14:09:58 UTC
I don't think if you have ldap use flag activated the expected behavior is "not to use ldap unless someone actually configures some sensible host". If you are not actually using ldap, just deactivate ldap use flag. Cheers, Ferdy I reopen this bug because now I've got a scenario where this behaviour is even more unexpected. I've got a system completely without ldap. One user asks for the gnupg ldap module to access ldap://keyserver.pgp.com, so I build gpg with the ldap USE flag. As a dependency, openldap is built, to provide ldap client libs. The openldap package provides the ldap use flag, so even if ldap is not included in make.conf, suddenly maildrop does not work any more. So I have a situation where just adding some feature to gnupg suddenly renders maildrop slow when it is updated next, which might be months in between. I am still of the opinion, that a USE flag should describe some feature made available, not force the sysadmins to actually configure and use this feature. You can always disable ldap USE flag for maildrop in /etc/portage/package.use. Or, you can investigate a bit and propose a change to default config that would fix this problem of yours. The bottom line is, don't enable USE flags you don't actually need. Not even "if you would one day like to use it". In fact with newer versions of maildrop this isn't a problem anymore since it uses courier-authlib. Cheers, Ferdy |