Re: [PATCH] crypt-gpgme: don't use gpg_* directly

To: Roman Kagan <rkagan@xxxxxxx>
Subject: Re: [PATCH] crypt-gpgme: don't use gpg_* directly
From: Michael Elkins <me@xxxxxxxxxxx>
Date: Thu, 30 Sep 2010 18:13:49 -0700
Cc: mutt-dev@xxxxxxxx
In-reply-to: <01731fb1884ea0e1eaf9.1285328353@xxxxxxxxxxxxxxxxxxxxxxx>
List-post: <mailto:mutt-dev@mutt.org>
List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-dev"
Mail-followup-to: Roman Kagan <rkagan@xxxxxxx>, mutt-dev@xxxxxxxx
References: <01731fb1884ea0e1eaf9.1285328353@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-mutt-dev@xxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)

On Fri, Sep 24, 2010 at 03:39:13PM +0400, Roman Kagan wrote:

# HG changeset patch
# User Roman Kagan <rkagan@xxxxxxx>
# Date 1285320318 -14400
# Node ID 01731fb1884ea0e1eaf9008ea9c70804b66f2363
# Parent  f467353f5657d9504dc5924fefc804fadc586f57
crypt-gpgme: don't use gpg_* directly

Since mutt uses gpgme, it should access all gpg functionality via gpgme_*
interfaces.  Otherwise link problems (either link errors or unnecessary
dependencies) arise.

Applied, thanks. I'd noticed this problem on Fedora because gpgme-configdidn't add -lgpg-error like it does in Debian/Ubuntu. I hadn't realized therewas a gpgme_strerror().

me

References:
- [PATCH] crypt-gpgme: don't use gpg_* directly
  - From: Roman Kagan

Prev by Date: Re: [Mutt] #3457: mutt crashes on accessing pop3 folder with message_cachedir option set
Next by Date: mutt: new changeset
Previous by thread: [PATCH] crypt-gpgme: don't use gpg_* directly
Next by thread: mutt: 22 new changesets
Index(es):
- Date
- Thread