OK, here is a set of 4 patches that implement the change over to the
gpgme library. There's quite a bit of work in there so I thought I'd
leave it as a few patches, but I have done some tidying.

I have some more ideas for improvements, but I'm happy that this
reproduces the behaviour of using the gpg binary, and I find sup usage
much smoother with this change.

I'll leave it for others to decide whether to stick this in sup 0.12 -
I guess it could be risky to stick it in without it being tested, but
maybe it could be applied to the next tree, and then moved to main
after 0.12 has been released.

Hamish Downer

>
> >> I am also working on having extra information generated when the key
> >> is not trusted, but this is not done yet. And I am also working on a
> >> hook where you can generate as much information as you want from the
> >> signature for the CryptoNotice. Hopefully be ready to submit before
> >> the weekend.
> >
> > This sounds nice. Thanks for your work!
>
> And thank you for your testing and patience :)
>
> The github version also has the sig-output hook set up. From the hook text:
>
> START
> Runs when the signature output is being generated, allowing you to
> add extra information to your signatures if you want.
>
> Variables:
> signature: the signature object (class is GPGME::Signature)
> from_key: the key that generated the signature (class is GPGME::Key)
>
> Return value: an array of lines of output
> END
>
> I've attached a sample hook file if you want to have a play with it.
> I'll document this all on the wiki if it gets accepted.
>
> I'll give you a few days to find some more problems, but if you fail
> to find any then I'll package this up as a single patch and resubmit
> it all.
>
> Hamish