All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: rongqing.li@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] pinentry: add recipes
Date: Fri, 19 Sep 2014 15:59:01 -0700	[thread overview]
Message-ID: <541CB535.9040405@gmail.com> (raw)
In-Reply-To: <1411109370-27814-1-git-send-email-rongqing.li@windriver.com>

This recipe already resides in meta-securty.

so I take it it should be removed from that layer?

- Armin


On 09/18/2014 11:49 PM, rongqing.li@windriver.com wrote:
> From: Roy Li <rongqing.li@windriver.com>
>
> gnupg 5.0 needs pinentry to work, refer to
> [http://rdist.root.org/2007/04/26/gpg-now-requires-pinentry-package/]
>
> Signed-off-by: Roy Li <rongqing.li@windriver.com>
> ---
>   meta/recipes-support/pinentry/pinentry_0.8.4.bb |   31 +++++++++++++++++++++++
>   1 file changed, 31 insertions(+)
>   create mode 100644 meta/recipes-support/pinentry/pinentry_0.8.4.bb
>
> diff --git a/meta/recipes-support/pinentry/pinentry_0.8.4.bb b/meta/recipes-support/pinentry/pinentry_0.8.4.bb
> new file mode 100644
> index 0000000..e20ebb3
> --- /dev/null
> +++ b/meta/recipes-support/pinentry/pinentry_0.8.4.bb
> @@ -0,0 +1,31 @@
> +SUMMARY = "Collection of simple PIN or passphrase entry dialogs"
> +DESCRIPTION = "\
> +	Pinentry is a collection of simple PIN or passphrase entry dialogs which \
> +	utilize the Assuan protocol as described by the aegypten project; see \
> +	http://www.gnupg.org/aegypten/ for details. \
> +	This package contains the curses (text) based version of the PIN entry dialog."
> +
> +HOMEPAGE = "http://www.gnupg.org/related_software/pinentry/index.en.html"
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=cbbd794e2a0a289b9dfcc9f513d1996e"
> +
> +DEPENDS = "libcap ncurses"
> +
> +inherit autotools
> +
> +SRC_URI = "ftp://ftp.gnupg.org/gcrypt/${BPN}/${BPN}-${PV}.tar.bz2 \
> +	"
> +
> +SRC_URI[md5sum] = "e2b6f94471ba1e978f6e5bf6b275189b"
> +SRC_URI[sha256sum] = "359db3bf46cb743ba0b3aeef259f6107271ca888ba3e22c1cba525c9aca35612"
> +
> +EXTRA_OECONF = "--disable-pinentry-gtk\
> +		--disable-pinentry-gtk2 \
> +		--disable-pinentry-qt \
> +		--disable-pinentry-qt4 \
> +		--with-ncurses-include-dir=${STAGING_LIBDIR}/.. \
> +		--disable-rpath \
> +		--disable-dependency-tracking \
> +		--disable-glibtest \
> +                --with-libcap=${STAGING_LIBDIR}/.. \
> +               "
>


  parent reply	other threads:[~2014-09-19 22:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19  6:49 [PATCH 1/2] pinentry: add recipes rongqing.li
2014-09-19 15:06 ` Burton, Ross
2014-09-22  0:27   ` Rongqing Li
2014-09-19 22:59 ` akuster808 [this message]
2014-09-19 23:04   ` Burton, Ross

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=541CB535.9040405@gmail.com \
    --to=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rongqing.li@windriver.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 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.