Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Barker <paul@paulbarker.me.uk>
To: OE Core <openembedded-core@lists.openembedded.org>
Subject: gpgme-config
Date: Wed, 23 Jul 2014 13:51:23 +0000	[thread overview]
Message-ID: <20140723135123.GA32767@gmail.com> (raw)

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

Hi all,

I'm trying to build opkg with 'gpg' added to PACKAGECONFIG on the master branch
of OE. The gpg support for opkg is provided by gpgme, which uses 'gpgme-config'
to determine CFLAGS and LIBS when building. After recent changes, the
gpgme-config script is now just a dummy and doesn't do anything.

Upstream gpgme do not provide a pkg-config file and an upstream issue about this
raised in 2012 was resolved WONTFIX (https://bugs.g10code.com/gnupg/issue1414).

Our options are:

1) Add a .pc file to gpgme and maintain it within OE as it is very unlikely to
   be accepted upstream. Then I need to modify configure.ac in opkg to support
   both this pkg-config file (for OE) and the gpgme-config utility (for all
   other users of opkg).

2) Make an exception to the policy on -config scripts for gpgme.

I haven't really followed the discussion on why -config scripts needed to be
removed so I'll put this question to other OE developers. Would option (2) cause
more problems in the long run? If so, is it worth the extra effort to follow
option (1)?

I'll probably need someone to bounce a few autoconf and pkg-config questions off
if I implement option (1) as I'm not very familiar with either system.

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-07-23 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 13:51 Paul Barker [this message]
2014-07-23 14:31 ` gpgme-config Richard Purdie
2014-07-23 14:49 ` gpgme-config Martin Jansa
2014-08-08 11:26   ` gpgme-config Paul Barker

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=20140723135123.GA32767@gmail.com \
    --to=paul@paulbarker.me.uk \
    --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