Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Fix gpg support in opkg
Date: Tue, 19 Aug 2014 21:29:52 +0200	[thread overview]
Message-ID: <20140819192952.GV3660@jama> (raw)
In-Reply-To: <20140819185526.GG7174@gmail.com>

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

On Tue, Aug 19, 2014 at 06:55:26PM +0000, Paul Barker wrote:
> On Fri, Aug 08, 2014 at 11:37:07AM +0000, Paul Barker wrote:
> > After recent changes to disable binconfig programs, 'gpgme-config' is no longer
> > installed with gpgme. This prevents opkg from finding gpgme which is needed when
> > 'gpg' is added to PACKAGECONFIG. This is fixed in two stages:
> > 
> >   - A 'gpgme.pc' file was created and added to openembedded-core to be installed
> >     with gpgme. The Cflags and Libs values for this file were found by running
> >     'gpgme-config' on my development machine. This patch is included here.
> > 
> >   - Changes were made to 'configure.ac' in opkg to use pkg-config to find gpgme
> >     instead of using 'gpgme-config'. These changes could be added as a patch in
> >     openembedded-core but I don't think there's much point. opkg-0.2.3 should be
> >     released in the next couple of weeks and I'll include the relevant changes
> >     in that.
> > 
> > Additionally, I found that gpg itself wasn't installed when opkg was installed
> > with gpg support. The 'opkg-key' program uses gpg to manage the list of trusted
> > keys so without gpg it isn't possible to set up package feed verification on a
> > device. Therefore, I've added 'gnupg' to RDEPENDS when 'gpg' is in
> > PACKAGECONFIG.
> > 
> > Paul Barker (2):
> >   gpgme: Add pkg-config file
> >   opkg: Add runtime dep on gnupg if 'gpg' is in PACAKGECONFIG
> > 
> >  meta/recipes-devtools/opkg/opkg.inc             |  2 +-
> >  meta/recipes-support/gpgme/gpgme-1.4.3/gpgme.pc | 10 ++++++++++
> >  meta/recipes-support/gpgme/gpgme_1.4.3.bb       |  8 +++++++-
> >  3 files changed, 18 insertions(+), 2 deletions(-)
> >  create mode 100644 meta/recipes-support/gpgme/gpgme-1.4.3/gpgme.pc
> > 
> 
> Ping on these two patches. I think I've addressed Martin's question on the
> second patch now, they should hopefully be ok to merge.

Yes, it's fine with me.

> Thanks,
> 
> -- 
> Paul Barker
> 
> Email: paul@paulbarker.me.uk
> http://www.paulbarker.me.uk



-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

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

      reply	other threads:[~2014-08-19 19:29 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
2014-08-19 18:55 ` [PATCH 0/2] Fix gpg support in opkg Paul Barker
2014-08-19 19:29   ` Martin Jansa [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=20140819192952.GV3660@jama \
    --to=martin.jansa@gmail.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