From: Armin Kuster <akuster808@gmail.com>
To: yocto@yoctoproject.org
Subject: [meta-security][PATCH] pinentry: remove from layer
Date: Tue, 30 Sep 2014 10:56:02 -0700 [thread overview]
Message-ID: <1412099762-4697-1-git-send-email-akuster808@gmail.com> (raw)
pinentry is now in oe-core so remove it from this layer.
Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
recipes-security/pinentry/pinentry_0.8.3.bb | 20 --------------------
1 file changed, 20 deletions(-)
delete mode 100644 recipes-security/pinentry/pinentry_0.8.3.bb
diff --git a/recipes-security/pinentry/pinentry_0.8.3.bb b/recipes-security/pinentry/pinentry_0.8.3.bb
deleted file mode 100644
index 0bd3021..0000000
--- a/recipes-security/pinentry/pinentry_0.8.3.bb
+++ /dev/null
@@ -1,20 +0,0 @@
-DESCRIPTION = "This is a collection of simple PIN or passphrase entry dialogs which utilize the Assuan protocol as described by the aegypten project"
-HOMEPAGE = "ftp://ftp.gnupg.org/gcrypt/"
-LICENSE = "GPL-2.0"
-LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
-DEPENDS = "glib-2.0 "
-
-SRC_URI = "ftp://ftp.gnupg.org/gcrypt/pinentry/${PN}-${PV}.tar.bz2"
-
-SRC_URI[md5sum] = "2ae681cbca0d9fb774b2c90b11ebf56c"
-SRC_URI[sha256sum] = "568b0b09b50b2388a4f94d704d5bcb28718ecd4654ed1acc43ab1f97d921a0ad"
-
-inherit autotools pkgconfig
-
-EXTRA_OECONF +="--disable-pinentry-gtk2 --disable-pinentry-qt \
- --disable-pinentry-qt4 --without-x "
-
-PACKAGECONFIG ??= "ncurses"
-
-PACKAGECONFIG[ncurses] = "--enable-ncurses --with-ncurses-include-dir=${STAGING_INCDIR}, '--disable-ncurses', ncurses"
-PACKAGECONFIG[libcap] = "--with-libcap, --without-libcap, libcap"
--
1.9.1
reply other threads:[~2014-09-30 17:56 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=1412099762-4697-1-git-send-email-akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.