notmuch/lib/Makefile.local, branch 0.19

lib: bump soname

2014-09-16T18:16:31Z

Adding return values to notmuch_database_close and notmuch_database_destroy may require bumping the soname.

lib: Bump library version from 3.0.0 to 3.1.0

2013-12-07T02:31:19Z

This version of the library introduces LIBNOTMUCH_CHECK_VERSION and the *_VERSION macros. Bumping the version number is also necessary to make the comment on LIBNOTMUCH_CHECK_VERSION no longer a lie.

lib: Make VERSION macros agree with soname version

2013-12-07T02:31:04Z

We have two distinct "library version" numbers: the soname version and the version macros. We need both for different reasons: the version macros enable easy compile-time version detection (and conditional compilation), while the soname version enables runtime version detection (which includes the version checking done by things like the Python bindings). However, currently, these two version numbers are different, which is unnecessary and can lead to confusion (especially in things like Debian, which include the soname version in the package name). This patch makes them the same by bumping the version macros up to agree with the soname version. (We should probably keep the version number in just one place so they can't get out of sync, but that can be done in another patch.)

lib/Makefile.local: depend on libs we are linking with

2013-01-22T12:59:33Z

lib: add date range query support

2012-10-31T19:55:32Z

Add a custom value range processor to enable date and time searches of the form date:since..until, where "since" and "until" are expressions understood by the previously added date/time parser, to restrict the results to messages within a particular time range (based on the Date: header). If "since" or "until" describes date/time at an accuracy of days or less, the values are rounded according to the accuracy, towards past for "since" and towards future for "until". For example, date:november..yesterday would match from the beginning of November until the end of yesterday. Expressions such as date:today..today means since the beginning of today until the end of today. Open-ended ranges are supported (since Xapian 1.2.1), i.e. you can specify date:..until or date:since.. to not limit the start or end date, respectively. CAVEATS: Xapian does not support spaces in range expressions. You can replace the spaces with '_', or (in most cases) '-', or (in some cases) leave the spaces out altogether. Entering date:expr without ".." (for example date:yesterday) will not work as you might expect. You can achieve the expected result by duplicating the expr both sides of ".." (for example date:yesterday..yesterday). Open-ended ranges won't work with pre-1.2.1 Xapian, but they don't produce an error either. Signed-off-by: Jani Nikula

build: build parse-time-string as part of the notmuch lib and static cli

2012-10-31T19:53:01Z

Support OpenBSD

2012-10-27T12:35:47Z

OpenBSD's build flags are identical to FreeBSD, except that libraries need to be explicitly linked against libc. No code changes are necessary. From: Cody Cutler

lib: Bump SO version from 2.0.0 to 3.0.0

2012-05-05T23:06:09Z

We've changed the APIs of notmuch_database_open, notmuch_database_create, and notmuch_database_close. Amended by db: also bump string in bindings/python/notmuch/globals.py

Don't link libnotmuch if libutil isn't linked in properly.

2011-11-19T19:18:05Z

For some reason, on my machine, the link is picking up /usr/lib/libutil.so instead of util/libutil.a. This causes there to be undefined symbols in libnotmuch, making it unuseable. This patch causes the link to fail instead.

Link libutil using filenmae, rather than using -l.

2011-11-13T18:58:21Z

glibc includes a libutil, so if the wrong -L options get passed, we will pick up glibc's version, rather than our own.