public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cURL dependencies broken
Date: Sun, 21 Jul 2019 12:41:00 -0000	[thread overview]
Message-ID: <5d345d6f.1c69fb81.6c59b.e89a@mx.google.com> (raw)
In-Reply-To: <87h87f27yl.fsf@Rainer.invalid>

On Sun, 21 Jul 2019 08:54:42, Achim Gratz wrote:
> No it doesn't.  The "requires" line is only there for backwards
> compatibility and is a join of all versioned dependencies, which are
> listed in "depends2".

Here is a culled cygcheck of cURL:

    $ cygcheck curl
    C:\cygwin64\bin\curl.exe
      C:\cygwin64\bin\cygcurl-4.dll
        C:\cygwin64\bin\cygcrypto-1.1.dll
        C:\cygwin64\bin\cygldap-2-4-2.dll
          C:\cygwin64\bin\cygcrypto-1.0.0.dll
          C:\cygwin64\bin\cygssl-1.0.0.dll
        C:\cygwin64\bin\cygssl-1.1.dll

So LibCurl itself is requiring the new version, but LibLdap is requiring old
version. Further, we can prove this with "setup.ini" as well. Look at culled
listing of LibCurl:

    @ libcurl4
    requires: ca-certificates cygwin libbrotlidec1 libopenldap2_4_2
    depends2: ca-certificates, cygwin, libbrotlidec1, libopenldap2_4_2

No matter which on we look at "libopenldap2_4_2" is required. Now, let go one
more step:

    @ libopenldap2_4_2
    requires: cygwin libopenssl100 libsasl2_3
    depends2: cygwin, libopenssl100, libsasl2_3

No matter which one we look at, the twice obsolete SSL is being used. Achim, in
the future, I think it would be helpful for you to check your facts before
posting.


--
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

  reply	other threads:[~2019-07-21 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-21  2:02 Steven Penny
2019-07-21  6:54 ` Achim Gratz
2019-07-21 12:41   ` Steven Penny [this message]
2019-07-21 17:21     ` Achim Gratz
2019-07-21 18:32       ` Steven Penny
2019-07-22 12:18         ` Jon Turney
2019-07-23  0:40     ` L A Walsh

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=5d345d6f.1c69fb81.6c59b.e89a@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).