Bug#787860: Bug#760102: gnome keyring & gpg agent

[Daniel Kahn Gillmor]

Control: forwarded 787860 https://bugzilla.gnome.org/show_bug.cgi?id=750468

On Fri 2015-06-05 15:33:35 -0400, Michael Biebl wrote:

> Since carrying patches downstream comes with a maintenance cost, we try
> to avoid that as much as possible.
> It thus would be great if you can forward this upstream, since this
> doesn't look like a Debian specific issue.
>
>> (the attached patch touches both ./configure.ac and ./configure -- since
>> the package appears to be doing autoreconf, maybe the modifications to
>> ./configure are unnecessary)
>> 
>> The only failures i'm now running into with seahorse like this are
>> failures due to gcr_importer hard-coding paths to gpg as well, so those
>> are bugs i'll file separately..
>
> Same here, would be great if you can file them also upstream.

I've now filed a more extensive changeset at seahorse upstream, as noted
above.

A more radical changeset might try to remove all reference to gnupg in
the seahorse codebase entirely, relying only on libgpgme as the
interface.

the HACKING file lists a number of situations where seahorse talks to
gpg directly, but none of them seem to apply any longer, fwict.

Someone who knows the seahorse history better than i do (Stef?) might
want to take a look to prune this down, it'd be nice to simplify things
here :)

Regards,

        --dkg