notmuch/configure, branch 0.29.1

configure: make _check_session_keys work with an as-needed linker

2019-05-20T21:34:12Z

When using a promiscuous linker, _check_session_keys was working fine. But some OSes (including some versions of Ubuntu) have set their linker to always link in "--as-needed" mode, which means that the order of the objects linked is relevant. If a library is loaded before it is needed, that library will no longer be linked in the final outcome. _check_session_keys.c was failing on those systems. Signed-off-by: Daniel Kahn Gillmor

configure: handle TEMP_GPG more robustly

2019-05-20T21:24:15Z

We never want ./configure to try to do something with an unassigned variable. So, make the directory $TEMP_GPG at the start of the testing of session-key handling, and clean it up afterwards as long as the directory exists. Signed-off-by: Daniel Kahn Gillmor

configure: better error handling on session key check.

2019-05-20T21:17:18Z

There are a few changes bundled here: * say "No." explicitly if there's a failure. * try to avoid implying that gpgme-config is necessary to build notmuch itself (it's not, though it may be useful if you need to rebuild gmime). * leave _check_session_keys and _check_session_keys.c around if ./configure fails, so that the user can play with it more easily for debugging. * let error messages show when _check_session_keys.c is built. Signed-off-by: Daniel Kahn Gillmor Amended by DB: use command -v instead of which.

configure: Ensure that GMime can extract session keys

2019-05-20T19:28:37Z

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

gmime-cleanup: no longer need to use GMime major version during build

2019-05-03T09:58:21Z

Signed-off-by: Daniel Kahn Gillmor

gmime-cleanup: always support session keys

2019-05-03T09:55:32Z

Our minimum version of GMime 3.0 always supports good session key handling. signed-off-by: Daniel Kahn Gillmor

build: drop support for gmime-2.6

2019-05-03T09:49:49Z

GMime 3.0 is over 2 years old now, and 2.6 has been deprecated in notmuch for about 1.5 years. Comments and documentation no longer need to refer to GMime 2.6, so clean them all up. Signed-off-by: Daniel Kahn Gillmor

Add a configure flag to disable rpaths

2019-03-12T23:12:49Z

Better support build environments where our /sbin/ldconfig based heuristic does not work (e.g. some musl libc based systems).

Merge tag '0.28.1'

2019-02-01T12:35:20Z

notmuch 0.28.1 release

configure: don't use special variable BASH

2019-02-01T11:59:12Z

bash, in it's wisdom, sets that variable when invoked as /bin/sh, but then doesn't act as bash, at least not to the degree we need to run scripts.