Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Jun 2005 20:49:41 +0400
From:      Boris Samorodov <bsam@ipt.ru>
To:        freebsd-ports@FreeBSD.org
Subject:   net/py-ldap2 and SASL
Message-ID:  <66624106@srv.sem.ipt.ru>

next in thread | raw e-mail | index | archive | help
--=-=-=

Hi!


I'm going to file a PR to get use of SASL libraries with net/py-ldap2
port. But before doing it I have a couple of questions.

Can anybody recall why was SASL support abandoned at the port? Were
there problems with building or using?

Next patch was good for me:


--=-=-=
Content-Disposition: inline; filename=patch
Content-Description: patch for net/py-ldap2

--- Makefile.orig	Wed Jun 22 17:20:17 2005
+++ Makefile	Wed Jun 22 19:43:19 2005
@@ -6,6 +6,7 @@
 
 PORTNAME=	ldap2
 PORTVERSION=	2.0.8
+PORTREVISON=	1
 CATEGORIES=	net
 MASTER_SITES=	${MASTER_SITE_SOURCEFORGE}
 MASTER_SITE_SUBDIR=	python-ldap
@@ -20,10 +21,56 @@
 USE_OPENLDAP=	yes
 USE_REINPLACE=	yes
 
+
+.include <bsd.port.pre.mk>
+
+
+.if defined(WANT_OPENLDAP_SASL) && !defined(WITHOUT_SASL)
+WITH_SASL=	yes
+.endif
+
+
+.if defined(WITH_SASL)
+LIB_DEPENDS=	ldap_r-2.2.7:${PORTSDIR}/net/openldap22-sasl-client
+.endif
+
+
+pre-everything::
+	@${ECHO} ${WANT_OPENLDAP_SASL}, ${WITHOUT_SASL}, ${WITH_SASL}
+	@${ECHO} "============================================================="
+	@${ECHO}
+	@${ECHO} "You can build ${PKGNAME} with the following options:"
+	@${ECHO}
+.if defined(WANT_OPENLDAP_SASL)
+	@${ECHO} "WITHOUT_SASL             without (Cyrus) SASL2 support"
+.else
+	@${ECHO} "WITH_SASL                with (Cyrus) SASL2 support"
+
+.endif
+	@${ECHO}
+	@${ECHO} "============================================================="
+	@${ECHO}
+
+
 do-configure:
-	@${REINPLACE_CMD} -e "s=/opt/openldap-OPENLDAP_REL_ENG_2_2/lib=${LOCALBASE}/lib=" \
+.if defined(WITH_SASL) && !defined(WITHOUT_SASL)
+	@${ECHO}
+	@${ECHO} Configuring ${PKGNAME} with SASL support
+	@${ECHO}
+	@${REINPLACE_CMD} -e "s=/opt/openldap-OPENLDAP_REL_ENG_2_2/lib=${LOCALBASE}/lib ${LOCALBASE}/lib/sasl2=" \
+		-e "s=/usr/include/sasl=${LOCALBASE}/include/sasl=" \
 		-e "s=/opt/openldap-OPENLDAP_REL_ENG_2_2/include=${LOCALBASE}/include=" \
+		${WRKSRC}/setup.cfg
+.else
+	@${ECHO}
+	@${ECHO} Configuring ${PKGNAME} without SASL support
+	@${ECHO}
+	@${REINPLACE_CMD} -e "s=/opt/openldap-OPENLDAP_REL_ENG_2_2/lib=${LOCALBASE}/lib=" \
 		-e "s=ldap_r lber ssl crypto sasl2=ldap_r lber ssl crypto=" \
+		-e "s=/opt/openldap-OPENLDAP_REL_ENG_2_2/include /usr/include/sasl=${LOCALBASE}/include=" \
 		${WRKSRC}/setup.cfg
+.endif
+
+
+.include <bsd.port.post.mk>
 
-.include <bsd.port.mk>

--=-=-=


I tried to use SASL auth with www/web2ldap (which depends on
net/py-ldap2) but got an error with diagnostic message someting like
"SASL authentication is not implemented".

After applying the patch and rebuilding/reinstalling I managed to auth
using SASL plain mechanism.

If anybody is interested in applying the patch a feedback is
appreciated.


WBR
-- 
bsam

--=-=-=--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?66624106>