Proposed Cyrus 2.3.13 branch (could be: "Re: [SVN] r768")

[Henrique de Moraes Holschuh]

On Mon, 09 Feb 2009, Duncan Gibb wrote:
> 1) I believe the choice of Berkeley DB version should be made at build
> time, rather than svn commit time.  To this end, I have changed
> debian/control so Cyrus build-depends on libdb4.4-dev | libdb4.5-dev |
> libdb4.6-dev and put the following mess into debian/rules
> 
>   export BDB_VERSION ?= $(shell dpkg-query -l 'libdb4.[2-6]-dev' | grep
> ^ii | sed -e 's|.*\s\libdb\(4\.[0-9]\)-dev\s.*|\1|')

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

Please revert this part of the change.  Pick whatever version of BDB
is the most stable across the main arches (x86, amd64, ppc...), which
often means asking the BDB maintainer about it, and go with that.
When in doubt, don't use anything openldap isn't using yet.

> 2) I allow epochs in the package name (we use them internally)
> 
> https://mail.incase.de/viewcvs/branches/cyrus23/cyrus-imapd-2.3-2.3.13/debian/cyrus-common-2.3.cyrus2.3.init?r1=767&r2=768

Good.

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

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

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

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh