From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: openldap
Date: Mon, 22 Jul 2019 23:28:00 -0000 [thread overview]
Message-ID: <5d36469c.1c69fb81.d30b3.1fe1@mx.google.com> (raw)
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
next reply other threads:[~2019-07-22 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 23:28 Steven Penny [this message]
2019-07-23 3:37 ` openldap Yaakov Selkowitz
-- strict thread matches above, loose matches on Subject: below --
2002-08-08 4:08 OpenLDAP Flynn
2002-08-08 4:31 ` OpenLDAP Robert Collins
2002-08-08 6:22 ` OpenLDAP Flynn
2000-11-14 9:28 OpenLDAP Emmanuel Blot
2000-11-14 18:05 ` OpenLDAP Jason Tishler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d36469c.1c69fb81.d30b3.1fe1@mx.google.com \
--to=svnpenn@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).