<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/T040-setup.sh, branch 0.34</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.34</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.34'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2021-03-27T12:26:14Z</updated>
<entry>
<title>CLI+lib: detect missing database in split configurations.</title>
<updated>2021-03-27T12:26:14Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-02-23T20:19:13Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=217f8196088f200972d35ee9181bfe361cccc04a'/>
<id>urn:sha1:217f8196088f200972d35ee9181bfe361cccc04a</id>
<content type='text'>
Eventually we want to do all opening of databases in the top
level (main function). This means that detection of missing databases
needs to move out of subcommands. It also requires updating the
library to use the new NO_DATABASE status code.
</content>
</entry>
<entry>
<title>test/setup: check file output instead of notmuch config list</title>
<updated>2021-03-27T12:26:14Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-02-27T14:50:33Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ee0e1cfb1748a11f14d7b5381b0fea55faac9567'/>
<id>urn:sha1:ee0e1cfb1748a11f14d7b5381b0fea55faac9567</id>
<content type='text'>
This allows verification of comments added to new / updated config
file.
</content>
</entry>
<entry>
<title>test/setup: add check for config exists, but no database.</title>
<updated>2021-03-18T11:03:19Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-03-14T14:01:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=9a5406cc94f26dfa4839bacaae80b94d4ad6739e'/>
<id>urn:sha1:9a5406cc94f26dfa4839bacaae80b94d4ad6739e</id>
<content type='text'>
This code path is not currently tested, and will need updating if the
location of the xapian database changes.
</content>
</entry>
<entry>
<title>cli/new: convert to new config framework</title>
<updated>2021-02-06T23:52:11Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-01-02T17:10:39Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0d3bef312dd624225825e6fe175ea8830c1c9e39'/>
<id>urn:sha1:0d3bef312dd624225825e6fe175ea8830c1c9e39</id>
<content type='text'>
In addition to the same type of changes as converting other
subcommands, add the possibility of creating a database at the top
level. It would probably make sense to use this for insert as well.
</content>
</entry>
<entry>
<title>gmime-cleanup: remove obsolete gpg_path configuration option and crypto contexts</title>
<updated>2019-05-03T09:55:04Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-02T13:19:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=096d45a878ba9606f1677f66d346b14c3c274fa5'/>
<id>urn:sha1:096d45a878ba9606f1677f66d346b14c3c274fa5</id>
<content type='text'>
Note that we do keep ignoring the gpg_path configuration option,
though, to avoid breakage of existing installations.  It is ignored
like any other unknown configuration option, but we at least document
that it is ignored so that people who find it in their legacy configs
can know that it's safe to drop.

signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>test: use $(dirname "$0") for sourcing test-lib.sh</title>
<updated>2017-10-20T22:52:49Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-09-25T20:38:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a863de1e43ee34f6f5794a2759fdceb287e851aa'/>
<id>urn:sha1:a863de1e43ee34f6f5794a2759fdceb287e851aa</id>
<content type='text'>
Don't assume the tests are always run from within the source tree.
</content>
</entry>
<entry>
<title>config: deprecate/drop crypto.gpg_path under gmime 2.6/3.0</title>
<updated>2017-07-15T00:23:52Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-07-14T13:12:00Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e142de643d3bb4354f70e1490a97b491d1116e95'/>
<id>urn:sha1:e142de643d3bb4354f70e1490a97b491d1116e95</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>lib: add built_with handling for XAPIAN_DB_RETRY_LOCK</title>
<updated>2016-06-29T07:05:49Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-06-26T15:29:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3a45d29ed4d753bcf72f2fa0bb37fefd4d18f96a'/>
<id>urn:sha1:3a45d29ed4d753bcf72f2fa0bb37fefd4d18f96a</id>
<content type='text'>
This support will be present only if the appropriate version of xapian
is available _and_ the user did not disable the feature when
building. So there really needs to be some way for the user to check.
</content>
</entry>
<entry>
<title>lib/cli: add library API / CLI for compile time options</title>
<updated>2016-05-13T10:29:12Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-03-22T10:54:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=792bea5aff135107fd970f51f3ef8c65f68194de'/>
<id>urn:sha1:792bea5aff135107fd970f51f3ef8c65f68194de</id>
<content type='text'>
This is intentionally low tech; if we have more than two options it may
make sense to build up what infrastructure is provided.
</content>
</entry>
<entry>
<title>test: make script exit (1) if it "fails" to source (.) a file</title>
<updated>2015-08-07T19:56:39Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2015-08-06T09:13:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=02a2eeb427d6b424029f6e5e5ddad4c6ec987741'/>
<id>urn:sha1:02a2eeb427d6b424029f6e5e5ddad4c6ec987741</id>
<content type='text'>
The files (test) scripts source (with builtin command `.`) provides
information which the scripts depend, and without the `source` to
succeed allowing script to continue may lead to dangerous situations
(e.g. rm -rf "${undefined_variable}"/*).

At the end of all source (.) lines construct ' || exit 1' was added;
In our case the script script will exit if it cannot find (or read) the
file to be sourced. Additionally script would also exits if the last
command of the sourced file exited nonzero.
</content>
</entry>
</feed>
