From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: gnupg2 ?
Date: Thu, 29 Jun 2017 10:17:00 -0000 [thread overview]
Message-ID: <b0a7b5e8-b434-e948-eaff-2eaf1127ef60@gmail.com> (raw)
In-Reply-To: <2ed91a25-083f-5ace-dee7-ae5bc6f57520@cygwin.com>
On 29/06/2017 08:27, Yaakov Selkowitz wrote:
> Marco,
>
> In order to update gpgme, we need libassuan in the distribution, as
> GnuPG 2 support is no longer optional. While I think we could get by
> with just that (and allow it to fall back to 1.x support at runtime), it
> did spur me to take another look at the gnupg2 stack. I don't know if
> it's *perfect* but it seems to be generally working:
>
> https://github.com/cygwinports/libassuan
> https://github.com/cygwinports/libksba
> https://github.com/cygwinports/npth
> https://github.com/cygwinports/gnupg2
> https://github.com/cygwinports/pinentry
> https://github.com/cygwinports/gpa
>
> Any chance you could test this out and/or be interested in maintaining
> some or all of it?
>
Hi Yaakov,
on my tests on 64 bit libassuan was always failing.
I looked inside the code and I saw a lot of
assumption on cygwin that seems not anymore, if ever, valid.
I will look on your proposal
Regards
Marco
next prev parent reply other threads:[~2017-06-29 10:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 6:27 Yaakov Selkowitz
2017-06-29 10:17 ` Marco Atzeri [this message]
2017-06-30 5:34 ` Marco Atzeri
2017-06-30 19:22 ` Andrew Schulman
2017-06-30 20:01 ` Marco Atzeri
2017-06-30 20:21 ` Yaakov Selkowitz
2017-07-01 4:29 ` Marco Atzeri
2017-07-11 21:12 ` Yaakov Selkowitz
2017-07-12 4:52 ` Marco Atzeri
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=b0a7b5e8-b434-e948-eaff-2eaf1127ef60@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).