Proposed Cyrus 2.3.13 branch

[Duncan Gibb]

Henrique de Moraes Holschuh wrote:

DG> I have changed debian/control so Cyrus build-depends on
DG> libdb4.4-dev | libdb4.5-dev | libdb4.6-dev

HdMH> Non-deterministic builds in face of random factors (like
HdMH> a screwed up chroot or whatever) are never a good idea.

HdMH> Please revert this part of the change.  Pick whatever
HdMH> version of BDB is the most stable across the main arches
HdMH> (x86, amd64, ppc...), which often means asking the BDB
HdHM> maintainer about it, and go with that.

I entirely agree with you that a release codebase (for Squeeze or for
Lenny-Backports) should be a deterministic build, using a specific BDB
version so everyone knows what they get and updates are uniform.  But I
also think that any such release version should be in its own stable
branch where those kinds of decisions can be made.  I don't think we're
ready to create those stable branches yet.

There are plenty of reasons why one might want to build with a different
BDB - not least to test the upgrade scripts we will have to write ;-)

If a particularly random user builds from an experimental SVN trunk in a
borked chroot and gets a package that doesn't 100% work, IMHO that's a
problem of their own making - albeit one we're interested in.


HdMH> When in doubt, don't use anything openldap isn't using yet.

OpenLDAP where?  The Debian slapd package (which only went to 2.4.11 in
Lenny after appeals for a version where complex syncrepl configs might
work) is still building against libdb4.2.  Whereas OpenLDAP upstream
recommends 4.7 (in which they've squashed a few bugs), with tolerance
down to 4.4.


Does anyone else have an opinion?


DG> I took out the huge and incomprehensible 99-update-autoconf.dpatch
DG> in favour of having debian/rules run autoconf and autoheader at
DG> build time.

HdMH> That's good, but use autoreconf instead, if possible.

OK; I will look into that.


HdMH> Also, autotooling at build time requires build-depending on
HdMH> a particular version of each of the required autofoo stuff,
HdMH> AND often build-conflicting with the old crufty ones.

Good point.  I will fix that.  I don't know what the situation with old
crufty autotools might be, because I don't think we've ever compiled
this codebase with anything older that whatever shipped with Sarge by
default.  Given that people build Cyrus on Solaris, we should be fairly
safe with old cruft ;-)


Cheers


Duncan

-- 
Duncan Gibb, Technical Director
Sirius Corporation plc - The Open Source Experts
http://www.siriusit.co.uk/ || +44 870 608 0063