On Fri, Sep 21, 2007 at 09:53:40AM +0200, Andreas Metzler wrote: > There are a couple of reasons why exim should not always automatically > use the latest and greatest bdb. exim is in base (Priority: standard). > > - The newest and latest bdb has not always been of sufficiently high > priority itself.[1]
Agreed, but this is a chicken-egg problem, and will be solved every time as a direct result of pam keeping up. > - IMHO base should try to limit itself to one version of bdb at a > time. There is no big win in exim switching, if e.g. libpam-modules > or libsasl2-2 (required by libldap2 which gnupg depends on) does > not. Agreed, and pam now build-depends on libdb-dev. Unfortunately, I think that openldap will be clinging to db4.2 for as long as it can. > - Users sometimes configure exim to pull data from other b-db using > software (e.g. DRAC for POP before SMTP) or use libberkeleydb-perl > to build databases for exim. Therefore these should really /try/ to > use bdb versions with compatible on-disk format. Since libberkeleydb-perl is already using a newer version of BDB than exim, I see more value in having both packages on the same version. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
