From: Rongqing Li <rongqing.li@windriver.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] gnupg: add pinentry RDEPENDS
Date: Tue, 23 Sep 2014 08:24:44 +0800 [thread overview]
Message-ID: <5420BDCC.8090704@windriver.com> (raw)
In-Reply-To: <20140922120004.GD32340@gmail.com>
On 09/22/2014 08:00 PM, Paul Barker wrote:
> On Mon, Sep 22, 2014 at 08:23:01AM +0800, Rongqing Li wrote:
>>
>>
>> On 09/19/2014 11:08 PM, Burton, Ross wrote:
>>> On 19 September 2014 07:49, <rongqing.li@windriver.com> wrote:
>>>> gnupg needs pinentry to run
>>>
>>> Isn't this only needed if the agent is enabled?
>>>
>>> Ross
>>>
>>>
>>
>>
>> No, gnupg 2.x.x always need it;
>>
>> 1. the below is from README of gnupg
>>
>> You also need the Pinentry package for most function of GnuPG; however
>> it is not a build requirement. Pinentry is available at
>> ftp://ftp.gnupg.org/gcrypt/pinentry/ .
>>
>
> There are some uses of gnupg which never need pinentry. For example, managing
> the set of trusted keys for verifying package and feed signatures with opkg. I'd
> prefer pinentry to be in RRECOMMENDS so that I can add it to
> BAD_RECOMMENDATIONS and thereby disable it when I know it isn't needed.
>
> Thanks,
>
I am ok, but I still hope the oe-core can accept the pinentry, since
"You also need the Pinentry package for most function of GnuPG" as in
gnupg README
-Roy
--
Best Reagrds,
Roy | RongQing Li
prev parent reply other threads:[~2014-09-23 0:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 6:49 [PATCH 2/2] gnupg: add pinentry RDEPENDS rongqing.li
2014-09-19 15:08 ` Burton, Ross
2014-09-22 0:23 ` Rongqing Li
2014-09-22 12:00 ` Paul Barker
2014-09-22 12:22 ` Burton, Ross
2014-09-23 0:24 ` Rongqing Li [this message]
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=5420BDCC.8090704@windriver.com \
--to=rongqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
/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