[Pkg-openldap-devel] Fwd: Berkeley DB transitions in openldap

[Ondřej Surý]

Resending to all openldap maintainers...


---------- Forwarded message ----------
From: Ondřej Surý <ondrej at sury.org>
Date: Fri, Apr 22, 2011 at 22:59
Subject: Berkeley DB transitions in openldap
To: Matthijs Möhlmann <matthijs at cacholong.nl>


Hi Matthijs,

I was looking at your commit for db5.1 transition and I was thinking
if you could adopt the system which hmh has created for cyrus-imapd to
keep track of Berkeley DB versions (and I have written automatic
upgrade script on top of that). We hardcode the version of Berkeley DB
to the file in the package at compile time to cyrus-db-types.txt and:

1. On first install we just copy cyrus-db-types.txt to cyrus-db-types.active
2. On any update we compare cyrus-db-types.txt to
cyrus-db-types.active and if they differ we do the upgrade and then
copy cyrus-db-types.txt to cyrus-db-types.active

I would be happy to help you write such script and adjust openldap
build system if you want. Also I think that dump&load is probably not
necessary (dump to /var/backup and calling dbX.Y_upgrade should be
enough).

This would have one advantage - automatic transitions to new Berkeley
DB versions (binNMUs would work) + hassle free upgrades from
debian-backports (if there is a backport compiled with different
(lower) version then it would break the upgrade based on openldap
version number).

So what do you think?

O.
--
Ondřej Surý <ondrej at sury.org>



-- 
Ondřej Surý <ondrej at sury.org>