Any update on this rather old bug?

[EMAIL PROTECTED] (Stefan Hornburg (Racke)) writes:

> libdb2 has performance and compatibility problems

I've just tried to compile it against libdb4.6, and the package builds
sucessfully:

diff -u courier-0.59.0/debian/control courier-0.59.0/debian/control
--- courier-0.59.0/debian/control
+++ courier-0.59.0/debian/control
@@ -4,7 +4,7 @@
 Original-Maintainer: Stefan Hornburg (Racke) <[EMAIL PROTECTED]>
 Standards-Version: 3.7.3
-Build-Depends: libmysqlclient15-dev, libpam0g-dev, libgdbm-dev | 
libgdbmg1-dev, libperl-dev, zlib1g-dev, libpcre3-dev, debhelper (>= 5.0.37), 
mime-support, libldap2-dev, procps, libsasl2-dev, expect, groff-base, gs | 
gs-aladdin, mgetty-fax, netpbm, libgamin-dev, libssl-dev, openssl (>= 0.9.6), 
libpq-dev, automake, libtool, courier-authlib-dev, po-debconf
+Build-Depends: libmysqlclient15-dev, libpam0g-dev, libdb4.6-dev, libperl-dev, 
zlib1g-dev, libpcre3-dev, debhelper (>= 5.0.37), mime-support, libldap2-dev, 
procps, libsasl2-dev, expect, groff-base, gs | gs-aladdin, mgetty-fax, netpbm, 
libgamin-dev, libssl-dev, openssl (>= 0.9.6), libpq-dev, automake, libtool, 
courier-authlib-dev, po-debconf
 Build-Conflicts: automake1.4
 
 Package: courier-base
diff -u courier-0.59.0/debian/rules courier-0.59.0/debian/rules
--- courier-0.59.0/debian/rules
+++ courier-0.59.0/debian/rules
@@ -39,7 +39,7 @@
                --without-socks \
                --enable-workarounds-for-imap-client-bugs \
                --with-authdaemonvar=/var/run/courier/authdaemon \
-               --with-db=gdbm \
+               --with-db=db \
                --without-fcgi \
                --with-htmllibdir=/usr/share/sqwebmail \
                --with-ispell=/usr/bin/ispell \


Are the performance concerns still valid? Can you perhaps give some
reference or at least more informations what your reasons for not
linking courier against libdb?

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to