From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] package: add gnupg
Date: Tue, 16 Oct 2012 22:05:01 +0200 [thread overview]
Message-ID: <20121016220501.727796ff@skate> (raw)
In-Reply-To: <507DB21F.1090506@mind.be>
On Tue, 16 Oct 2012 21:14:39 +0200, Arnout Vandecappelle wrote:
> I think this is the reason why gnupg wasn't included before. My
> colleague Stijn submitted a patch series for a more recent version of
> gnupg a while ago, and that also faced a portability problem (in the
> 'portable threads library :-) Thomas suggested to wait for npth-based
> gnupg 2.1, but that one hasn't been released yet.
I think the problem with Stinj version was due to the usage of gnupg
2.x, and I suggested to either wait for 2.1 to solve the usage of the
non-portable pth library, or fall back to an older version such as
1.4.x, which Peter did.
That said, my memories on this are quite blurry, so I might be wrong
here. I'd have to look through the archives.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-10-16 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 8:20 [Buildroot] [git commit] package: add gnupg Peter Korsgaard
2012-10-16 16:56 ` Thomas Petazzoni
2012-10-16 19:04 ` Peter Korsgaard
2012-10-16 19:14 ` Arnout Vandecappelle
2012-10-16 19:24 ` Yann E. MORIN
2012-10-16 20:05 ` Thomas Petazzoni [this message]
2012-10-16 21:00 ` Peter Korsgaard
2012-10-16 21:03 ` Gustavo Zacarias
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=20121016220501.727796ff@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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