Date: Tue, 10 Jan 2017 11:11:23 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> To: Franco Fichtner <franco@lastsummer.de> Cc: Jan Bramkamp <crest@rlwinm.de>, freebsd-ports@freebsd.org Subject: Re: openldap-client vs openldap-sasl-client Message-ID: <5874B34B.5000705@quip.cz> In-Reply-To: <6DB678CD-572C-4E88-9009-3E95032B9AF3@lastsummer.de> References: <c798f1e9-92f0-1d2a-32e4-46dad59f05d0@FreeBSD.org> <34b66662-a2d7-706d-3653-e0ffc9bf81b2@rlwinm.de> <5874135B.4000900@quip.cz> <587414A3.1010206@quip.cz> <6DB678CD-572C-4E88-9009-3E95032B9AF3@lastsummer.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Franco Fichtner wrote on 2017/01/10 06:48: > >> On 9 Jan 2017, at 11:54 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >> >> I don't need SASL for LDAP client, but somebody messed up ports tree with WANT_OPENLDAP_SASL which is for users and not maintainers: >> >> # WANT_OPENLDAP_SASL >> # - User-defined variable to depend upon SASL-enabled OpenLDAP >> # client. Must NOT be set in a port Makefile. > > This note was added two days ago and it's simply not correct, > and/or overcome by events as it is against the common practice > in the tree *and* adhering to it would break currently working > ports. Even if this doesn't exist at all the change was bad handled. No info in UPDATING and what was working for years now doesn't work. Simple "pkg upgrade" failed because of conflicting versions of openldap-client. > OpenLDAP needs framework improvements of the sort that gssapi > or ssl received, but we have yet to hear from the maintainer of > OpenLDAP on the matter. And changes like this must be better tested before committing... Breakages are too common in these days. Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5874B34B.5000705>