DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:to:subject:content-type;
	 q=dns; s=default; b=vMROyiMdx4o889cBN4xtg8iSNdZvu59SrPd9xRsthco
	zNXvvQ6bdzVsJj427DqlavSYM0zfoeJxWzGPESjuNzPCNT8BNYxqhEkG+WXLmUZ6
	ll3DYFzttV6VC2JAjZwVjW/F3LjIZTEVJuCnn5J1OIZOZxMarFzYl+uQG4QBjWnY
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <5d36469c.1c69fb81.d30b3.1fe1@mx.google.com>
Date: Mon, 22 Jul 2019 16:28:28 -0700 (PDT)
From: Steven Penny <svnpenn AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: openldap
Content-Type: text/plain; charset=utf8; format=flowed
User-Agent: Suede Mail/2.8.0 (github.com/cup/suede)

OpenLdap looks to be currently abandoned:

https://cygwin.com/cygwin-pkg-maint

This is an issue because it can (and currently is) used by Cygwin cURL build:

https://github.com/cygwinports/curl/blob/2e953092/curl.cygport#L55

I think the best solution at this time is to simply remove OpenLdap from cURL
builds until this is resolved. Failing that, I can volunteer to take up
maintenance of OpenLdap if it really need to be kept along. However I am not
sure this is the case, as my understand is OpenLdap is only used in these type
cases:

    curl ldaps://ldap.foo.com

https://stackoverflow.com/questions/44546116

and wouldnt change anything with regard to standard HTTP/HTTPS/FTP etc
protocols. Personally I have never used OpenLdap so I could care less if its
removed. But again I can respect if we have a significant amount of users that
need it.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple