aboutsummaryrefslogtreecommitdiff
path: root/test/T040-setup.sh
diff options
context:
space:
mode:
authorDaniel Kahn Gillmor <dkg@fifthhorseman.net>2017-07-14 15:12:00 +0200
committerDavid Bremner <david@tethera.net>2017-07-14 21:23:52 -0300
commite142de643d3bb4354f70e1490a97b491d1116e95 (patch)
treecb192df604b692bc415584c2c66e993efa6a7864 /test/T040-setup.sh
parent8492298a613e8e666d0f3054dadcb98b72a65ae4 (diff)
config: deprecate/drop crypto.gpg_path under gmime 2.6/3.0
gmime 3.0 no longer offers a means to set the path for gpg. Users can set $PATH anyway if they want to pick a differently-installed gpg (e.g. /usr/local/bin/gpg), so this isn't much of a reduction in functionality. The one main difference is for people who have tried to use "gpg2" to make use of gpg 2.1, but that isn't usefully co-installable anyway.
Diffstat (limited to 'test/T040-setup.sh')
-rwxr-xr-xtest/T040-setup.sh8
1 files changed, 7 insertions, 1 deletions
diff --git a/test/T040-setup.sh b/test/T040-setup.sh
index 021f2d0b..998bd6e0 100755
--- a/test/T040-setup.sh
+++ b/test/T040-setup.sh
@@ -19,6 +19,12 @@ another.suite@example.com
foo bar
baz
EOF
+
+if [ "${NOTMUCH_GMIME_MAJOR}" -lt 3 ]; then
+ config_gpg_path="crypto.gpg_path=gpg
+"
+fi
+
output=$(notmuch --config=new-notmuch-config config list | notmuch_built_with_sanitize)
test_expect_equal "$output" "\
database.path=/path/to/maildir
@@ -29,7 +35,7 @@ new.tags=foo;bar;
new.ignore=
search.exclude_tags=baz;
maildir.synchronize_flags=true
-crypto.gpg_path=gpg
+""${config_gpg_path}""\
built_with.compact=something
built_with.field_processor=something
built_with.retry_lock=something"