From: Michael Grzeschik <m.grzeschik@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH v2] gnupg: version bump to 2.0.22 and add bz2 support
Date: Fri, 11 Oct 2013 15:37:22 +0200 [thread overview]
Message-ID: <1381498642-25283-1-git-send-email-m.grzeschik@pengutronix.de> (raw)
The gnupg in ptxdist is not supposed to generate keys. Keys from other
systems will likely have a lot cypher and compression options enabled.
To support and use such keys we shall enable all options in the library,
including bz2.
Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
---
rules/gnupg.in | 2 ++
rules/gnupg.make | 6 +++---
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/rules/gnupg.in b/rules/gnupg.in
index 1f6c150..164a9dc 100644
--- a/rules/gnupg.in
+++ b/rules/gnupg.in
@@ -8,6 +8,8 @@ config GNUPG
select LIBGCRYPT
select LIBKSBA
select READLINE
+ select BZIP2
+ select BZIP2_LIBBZ2
select ZLIB
help
GnuPG - The GNU Privacy Guard suite of programs
diff --git a/rules/gnupg.make b/rules/gnupg.make
index 0ee87ef..ddcd268 100644
--- a/rules/gnupg.make
+++ b/rules/gnupg.make
@@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_GNUPG) += gnupg
#
# Paths and names
#
-GNUPG_VERSION := 2.0.15
-GNUPG_MD5 := c1286e85b66349879dc4b760dd83e2f1
+GNUPG_VERSION := 2.0.22
+GNUPG_MD5 := ee22e7b4fdbfcb50229c2e6db6db291e
GNUPG := gnupg-$(GNUPG_VERSION)
GNUPG_SUFFIX := tar.bz2
GNUPG_URL := ftp://ftp.gnupg.org/gcrypt/gnupg/$(GNUPG).$(GNUPG_SUFFIX)
@@ -49,7 +49,7 @@ GNUPG_CONF_OPT := $(CROSS_AUTOCONF_USR) \
--disable-nls \
--disable-rpath \
--disable-regex \
- --disable-bzip2
+ --enable-bzip2
ifndef PTXCONF_ICONV
GNUPG_AUTOCONF += --without-libiconv-prefix
--
1.8.4.rc3
--
ptxdist mailing list
ptxdist@pengutronix.de
reply other threads:[~2013-10-11 13:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1381498642-25283-1-git-send-email-m.grzeschik@pengutronix.de \
--to=m.grzeschik@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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