Re: new gmime/gpg bug



Am 04.07.04 18:20 schrieb(en) Pawel Salek:
I guess I can commit that patch if gmime-2.1.5 does not break anything else: I trust your judgement!

To be honest, I currently don't see a reason why this patch should be committed (if it still applies cleanly). It *requires* gmime 2.1.5 or above due to the gmime crypto api changes, but it doesn't improve the situation on the crypto side at all. I don't think it will break anything elsewhere, though, at least if we don't add GMIME_DISABLE_DEPRACTED to the flags.


If Jeff produces a working gmime rfc 3156 implementation, I will of course be happy to submit a new patch!

Cheers, Albrecht.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Albrecht Dreß  -  Johanna-Kirchner-Straße 13  -  D-53123 Bonn (Germany)
      Phone (+49) 228 6199571  -  mailto:albrecht dress arcor de
_________________________________________________________________________

Attachment: pgphpgy2FjlwY.pgp
Description: PGP signature



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]