Bug#442645: exim4: newer BDB

[Andreas Metzler]

On 2007-09-20 Clint Adams <schizo at debian.org> wrote:
> On Thu, Sep 20, 2007 at 07:29:03PM +0200, Marc Haber wrote:
>> Exim's default config only uses Berkeley DB files for transient data
>> such as retry hints, and the postinst code simply removes all db files
>> that exim_dumpdb gives a non-zero reply code for.
 
>> If the local admin decides to use db files for some input lists, they
>> need to do manual work.

> So build-depending on libdb-dev should mean you wouldn't need to change
> the b-d ever again unless there's an incompatible API change that isn't
> handled by the upstream code.  Furthermore, it would be possible to
> switch to a newer version with just a binNMU.

> Given your transient data description, I doubt there will be any trouble
> with you always keeping up with what is deemed the "current" version.

Hello,

I think so too. However I think we should keep manually updating when
necessary

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]

- 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.

- 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.

cu andreas

[1] Like currently in sid.
Package: libpam-modules
Priority: required
Depends: libc6 (>= 2.6-1), libcap1, libdb4.6, libpam0g (>= 0.99.7.1),
    libselinux1 (>= 2.0.15)

Package: libdb4.6
Priority: standard
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'