[PATCH 0/5] Cleanups for the GPGME crypto backend

Kevin J. McCarthy kevin at 8t8.us
Wed Dec 5 17:40:41 UTC 2018


On Wed, Dec 05, 2018 at 09:22:00AM +0100, ilf wrote:
>I agree. When Mutt gets patches now, they should work for current - or 
>only slightly - older GPGME versions. The most prominent reason to use 
>older releases are OS distros that ship and support releases from the 
>time of their freeze. But if they don't upgrade GPGME, then they don't 
>update Mutt either.
>
>GPGME 1.8.0 has been released two years ago. I think it's very 
>reasonable to have a future Mutt release to require that version.
>
>At least by default. If anyone has a valid use-case maybe a fallback 
>option could support 1.6.0, which is over three years old.

Unfortunately, some users compile Mutt on their older systems, because 
they want the new features.  The more we increase the requirements, the 
more users and testers we lose.

One of my best testers, @chsiza on gitlab, runs on a Mac and regularly 
tests the latest commits.  Mac's ports libraries are notoriously out of 
date.

So I'd like to stay conservative on the _hard_ system requirements.  I 
think 1.4.0 is pretty reasonable, but I start to get nervous about 
requiring newer than that.

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.mutt.org/pipermail/mutt-dev/attachments/20181205/18cb2e9b/attachment.asc>


More information about the Mutt-dev mailing list