From: Daniel Kahn Gillmor Date: Mon, 6 May 2019 20:16:55 +0000 (-0400) Subject: configure: Ensure that GMime can extract session keys X-Git-Tag: archive/debian/0.29_rc0-1~50 X-Git-Url: https://git.notmuchmail.org/git?a=commitdiff_plain;ds=sidebyside;h=30c4fa3702f90572afcd1984dbd7aba70f2b4fd9;hp=30c4fa3702f90572afcd1984dbd7aba70f2b4fd9;p=notmuch configure: Ensure that GMime can extract session keys GMime 3.0 and higher can extract session keys, but it will *not* extract session keys if it was built with --disable-crypto, or if it was built against GPGME version < 1.8.0. Notmuch currently expects to be able to extract session keys, and tests will fail if it is not possible, so we ensure that this is the case during ./configure time. Part of this feels awkward because notmuch doesn't directly depend on gpg at all. Rather, it depends on GMime, and the current implementation of GMime depends on GPGME for its crypto, and GPGME in turn depends on gpg. So the use of gpg in ./configure isn't actually introducing a new dependency, though if a future version of GMime were ever to move away from GnuPG, we might need to reconsider. Note that this changeset depends on id:20190506174327.13457-1-dkg@fifthhorseman.net , which supplies the rfc822 message test/corpora/crypto/basic-encrypted.eml used in it. Signed-off-by: Daniel Kahn Gillmor ---