Date: Thursday, February 6, 2014 @ 21:16:16 Author: andyrtr Revision: 205536
dropping Berkeley DB support isn't possible currently - but it seems smp safe to build Modified: openldap/trunk/PKGBUILD ----------+ PKGBUILD | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) Modified: PKGBUILD =================================================================== --- PKGBUILD 2014-02-06 19:58:31 UTC (rev 205535) +++ PKGBUILD 2014-02-06 20:16:16 UTC (rev 205536) @@ -9,7 +9,7 @@ url="http://www.openldap.org/" license=('custom') makedepends=('libltdl' 'libsasl' 'e2fsprogs' 'util-linux' 'chrpath') -options=('!makeflags') +#options=('!makeflags') source=(ftp://ftp.openldap.org/pub/OpenLDAP/openldap-release/${pkgbase}-${pkgver}.tgz slapd.service slapd.tmpfiles openldap-ntlm.patch) sha1sums=('2b8e8401214867c361f7212e7058f95118b5bd6c' @@ -17,6 +17,11 @@ '59241a813d7508294e4ef1cec3bfe1f5495e109d' 'e4afd9f1c810ef4c4cd8fe1101dfe5887f2b7eef') +# see http://www.openldap.org/faq/data/cache/756.html +# there's no proper backend support for anything apart from +# BerkeleyDB, if we don't want to drop local backend server support +# we are forced to keep Berkeley DB here + prepare() { cd ${pkgbase}-${pkgver} patch -p1 -i "${srcdir}"/openldap-ntlm.patch