Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Barker <paul@paulbarker.me.uk>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] opkg: Add runtime dep on gnupg if 'gpg' is in PACAKGECONFIG
Date: Thu, 14 Aug 2014 17:19:06 +0000	[thread overview]
Message-ID: <20140814171906.GG13399@gmail.com> (raw)
In-Reply-To: <20140814171653.GN14848@jama>

[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]

On Thu, Aug 14, 2014 at 07:16:53PM +0200, Martin Jansa wrote:
> On Thu, Aug 14, 2014 at 04:50:33PM +0000, Paul Barker wrote:
> > On Fri, Aug 08, 2014 at 12:16:28PM +0000, Paul Barker wrote:
> > > On Fri, Aug 08, 2014 at 02:13:46PM +0200, Martin Jansa wrote:
> > > > On Fri, Aug 08, 2014 at 11:37:09AM +0000, Paul Barker wrote:
> > > > > The 'opkg-key' utility requires gpg to manage the list of trusted keys. The
> > > > > ability to verify package signatures is not much use without the ability to add
> > > > > keys to the trusted list...
> > > > > 
> > > > > Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
> > > > > ---
> > > > >  meta/recipes-devtools/opkg/opkg.inc | 2 +-
> > > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > > 
> > > > > diff --git a/meta/recipes-devtools/opkg/opkg.inc b/meta/recipes-devtools/opkg/opkg.inc
> > > > > index ba21d84..56c54b6 100644
> > > > > --- a/meta/recipes-devtools/opkg/opkg.inc
> > > > > +++ b/meta/recipes-devtools/opkg/opkg.inc
> > > > > @@ -27,7 +27,7 @@ OPKGLIBDIR = "${target_localstatedir}/lib"
> > > > >  
> > > > >  PACKAGECONFIG ??= ""
> > > > >  
> > > > > -PACKAGECONFIG[gpg] = "--enable-gpg,--disable-gpg,gpgme libgpg-error"
> > > > > +PACKAGECONFIG[gpg] = "--enable-gpg,--disable-gpg,gpgme libgpg-error,gnupg"
> > > > 
> > > > Shouldn't this be gpgme?
> > > > 
> > > 
> > > Which bit? The PACKAGECONFIG name or one of the comma separated fields?
> > > 
> > 
> > Sorry Martin, I didn't understand your comment. Could you clarify for me?
> 
> Sorry for late reply, I haven't noticed your earlier e-mail.
> 
> It has build-time dependency on gpgme and runtime dependency on gnupg
> (in comma separated fields) - it could be OK, I just wasn't sure.
> 
> Is opkg-key calling gnupg tools?
> 

Yes, opkg-key is just a shell script which runs 'gpg' with appropriate command
line options. The main opkg program uses the gpgme library instead.

Thanks,

-- 
Paul Barker

Email: paul@paulbarker.me.uk
http://www.paulbarker.me.uk

[-- Attachment #2: Type: application/pgp-signature, Size: 484 bytes --]

  reply	other threads:[~2014-08-14 17:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08 11:37 [PATCH 0/2] Fix gpg support in opkg Paul Barker
2014-08-08 11:37 ` [PATCH 1/2] gpgme: Add pkg-config file Paul Barker
2014-08-08 11:37 ` [PATCH 2/2] opkg: Add runtime dep on gnupg if 'gpg' is in PACAKGECONFIG Paul Barker
2014-08-08 12:13   ` Martin Jansa
2014-08-08 12:16     ` Paul Barker
2014-08-14 16:50       ` Paul Barker
2014-08-14 17:16         ` Martin Jansa
2014-08-14 17:19           ` Paul Barker [this message]
2014-08-19 18:55 ` [PATCH 0/2] Fix gpg support in opkg Paul Barker
2014-08-19 19:29   ` Martin Jansa

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=20140814171906.GG13399@gmail.com \
    --to=paul@paulbarker.me.uk \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox