public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: [ITA] libev, libevent, libmetalink
Date: Mon, 31 May 2021 17:40:03 -0600	[thread overview]
Message-ID: <54383186-a1d7-e92f-c7e2-15c3ef1abe22@SystematicSw.ab.ca> (raw)

Some more curl library sub-/dependencies I'd like to adopt, with links 
to Appveyor CI builds and logs, and Cygwin packages on Google drive:

libev                                        ORPHANED (Yaakov Selkowitz)

last 4.22	-> proposed 4.33

libev4
libev-devel
libev-debuginfo

https://ci.appveyor.com/project/cygwin/scallywag/builds/39388956

https://drive.google.com/drive/folders/1EnLpN4L6H44FZSBzKPB21i9r6qTClNzZ

libevent                                     ORPHANED (Yaakov Selkowitz)
mingw64-i686-libevent                        ORPHANED (Yaakov Selkowitz)
mingw64-x86_64-libevent                      ORPHANED (Yaakov Selkowitz)

last 2.0.22	-> proposed 2.1.12

libevent2.0_5
libevent-devel
libev-debuginfo

mingw64-i686-libevent
mingw64-x86_64-libevent

https://ci.appveyor.com/project/cygwin/scallywag/builds/39388912

https://drive.google.com/drive/folders/1mloeZ1-GmaS2Dtc0prC_mXANpEGoH86M


libmetalink                                  ORPHANED (Yaakov Selkowitz)

last 0.1.2	-> proposed 0.1.3

libmetalink3
libmetalink-devel
libmetalink-debuginfo

https://ci.appveyor.com/project/cygwin/scallywag/builds/39394216

https://drive.google.com/drive/folders/18xT5BVPiCeqd654AZsGuCdb93hVHPZQd

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

             reply	other threads:[~2021-05-31 23:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 23:40 Brian Inglis [this message]
2021-06-01 17:48 ` Marco Atzeri
2021-06-01 22:35   ` Brian Inglis

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=54383186-a1d7-e92f-c7e2-15c3ef1abe22@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin-apps@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).