Date: Mon, 08 Aug 2016 17:52:29 +0000
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 211142] net/samba4{2,3,4}: ADS option should enforce (imply) WANT_OPENLDAP_SASL
Message-ID: <bug-211142-13-RFfIjhY0lJ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211142-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-211142-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211142 --- Comment #10 from prj@rootwyrm.com --- (In reply to Mark Felder from comment #8) Yep. I was hoping to stop-gap (this is blocking security/sssd improvements)= but the same issue seen here was not reproducing in clean tree for me. I'm confident saying there is definitely something misbehaving in bsd.ldap.mk a= nd the current state of it is now actively blocking multiple items. The 'easy' fix is for ADS to be removed from the samba4{2,3,4} OPTIONS_DEFA= ULT. But removing ADS from OPTIONS_DEFAULT has extreme impacts - not only does it affect any port making use of samba4*, but it will completely cripple expec= ted default functionality of samba itself. DEFAULT_VERSIONS is obviously preferable, but unless it can reliably force WANT_OPENLDAP_SASL, it would not address the issue here. Not only that, but frankly, I don't see a sound reason for it. bsd.ldap.mk still allows 2.3, b= ut all of those ports expired in 2013 it turns out. So as it is bsd.ldap.mk sh= ould be considered broken.=20 At current, it looks like there are 92 ports (including expired ports) which depend on openldap24-client, and zero conflicts with either port. Since SASL extends functionality, rather than changes, is there any reason to not remo= ve bsd.ldap.mk, combine openldap24-client and openldap24-sasl-client, and make SASL OPTIONS_DEFAULT for the openldap port? (I'm sure there probably was, b= ut it seems far less likely now.) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211142-13-RFfIjhY0lJ>