From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] libidn2 libpsl publicsuffix-list
Date: Fri, 21 May 2021 21:54:02 +0200 [thread overview]
Message-ID: <33fd5c2a-0f86-0708-ccf7-1d5c5fad9860@gmail.com> (raw)
In-Reply-To: <a4717a06-b819-830b-6826-c433ce892f26@SystematicSw.ab.ca>
On 21.05.2021 20:29, Brian Inglis wrote:
> Noticing some libraries used by curl and wget/2 other than libssh2
> that were outdated and orphaned, I decided to take a look at building
> updates and would now like to adopt them.
>
> The list below shows the distributed packages, links to the Appveyor CI
> builds and logs for those who prefer looking at those, and links
> to Google drive folders with all the usual files and archives for others.
>
> Feedback and questions welcome.
>
>
> libidn2
> mingw64-i686-libidn2
> mingw64-x86_64-libidn2
I need only the main packages
> https://ci.appveyor.com/project/cygwin/scallywag/builds/39238560
>
> https://drive.google.com/drive/folders/1AtV2eRZexLWCczuThQP2rTUj3ZfC2Y56
>
> libpsl
also mingw64 ?
> https://ci.appveyor.com/project/cygwin/scallywag/builds/39260268
>
> https://drive.google.com/drive/folders/1-4nIHGt59ZYS9xA7wVJ1JNwmAwIHwhn1
>
> publicsuffix-list
OK
> https://ci.appveyor.com/project/cygwin/scallywag/builds/39259635
>
> https://drive.google.com/drive/folders/1fTekDj6YGr6bq245eqGrlANUBobD-TtL
>
> [I still need to look further at problems (upstream) with the older libidn,
> and may pick that up also later.]
when you want ;-)
You are the new maintainer for these
Thanks
Marco
next prev parent reply other threads:[~2021-05-21 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 18:29 Brian Inglis
2021-05-21 19:54 ` Marco Atzeri [this message]
2021-05-21 23:21 ` 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=33fd5c2a-0f86-0708-ccf7-1d5c5fad9860@gmail.com \
--to=marco.atzeri@gmail.com \
--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).