<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/configure, branch 0.15.2</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.15.2</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.15.2'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2012-12-01T12:04:30Z</updated>
<entry>
<title>configure: really expand libdir_expanded</title>
<updated>2012-12-01T12:04:30Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2012-11-28T12:25:52Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3c6b2d5071fb71035d5d8cfd24b3bb843840eb9b'/>
<id>urn:sha1:3c6b2d5071fb71035d5d8cfd24b3bb843840eb9b</id>
<content type='text'>
It turns out that if people really use configure in autotools style and pass
libdir containing '${prefix}/foo' then the ldconfig previously failed.

This uses sed for portability (versus bash parameter expansion with
substitution) and hopefully a bit more robustness than blindly
parameter expanding the string.
</content>
</entry>
<entry>
<title>build: drop the -Wswitch-enum warning</title>
<updated>2012-10-31T19:39:25Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2012-10-30T20:32:32Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c158201ee217740cb1b64858df8c7d39cf7793d0'/>
<id>urn:sha1:c158201ee217740cb1b64858df8c7d39cf7793d0</id>
<content type='text'>
-Wswitch-enum is a bit awkward if a switch statement is intended to
handle just some of the named codes of an enumeration especially, and
leave the rest to the default label.

We already have -Wall, which enables -Wswitch by default, and per GCC
documentation, "The only difference between -Wswitch and this option
[-Wswitch-enum] is that this option gives a warning about an omitted
enumeration code even if there is a default label."

Drop -Wswitch-enum to not force listing all named codes of
enumerations in switch statements that have a default label.
</content>
</entry>
<entry>
<title>Support OpenBSD</title>
<updated>2012-10-27T12:35:47Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-10-24T21:43:28Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b04c062aee50f456f46bf7f31641384010780791'/>
<id>urn:sha1:b04c062aee50f456f46bf7f31641384010780791</id>
<content type='text'>
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 &lt;ccutler@csail.mit.edu&gt;
</content>
</entry>
<entry>
<title>configure: Add support for FreeBSD.</title>
<updated>2012-09-02T02:15:53Z</updated>
<author>
<name>Mike Kelly</name>
<email>pioto@pioto.org</email>
</author>
<published>2012-05-30T07:01:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=df6f3cdf9d421011090ccb50af9828f5903544ee'/>
<id>urn:sha1:df6f3cdf9d421011090ccb50af9828f5903544ee</id>
<content type='text'>
This makes FreeBSD a recognized platform. Follow up patches make it
work properly.
</content>
</entry>
<entry>
<title>configure: check whether shell is capable of parameter substring processing</title>
<updated>2012-07-25T11:17:24Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2012-05-03T18:59:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4cedb2a3ea77b61a5d8e9fe56e8585d312ee96ca'/>
<id>urn:sha1:4cedb2a3ea77b61a5d8e9fe56e8585d312ee96ca</id>
<content type='text'>
'configure' script uses parameter substring extensively. It is Posix shell
feature. Original Bourne shell does not have such features. Some systems
still ships such shells as /bin/sh (for compatibility reasons -- shell
scripts written on those platforms are expected to work on 1990's systems).

Just testing whether parameter substring processing works will make the
shell exit due to syntax error if it is not compatible. Therefore the test
is executed in a subshell -- subshell exits with nonzero value when the
operation in question fails.

As 'if ! ...' does not work in Bourne shell, Short-circuiting construct
'||' is used to print information message and exit when expected.
</content>
</entry>
<entry>
<title>config: add quoting to fix IFS bug</title>
<updated>2012-06-03T16:26:44Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2012-06-02T18:16:01Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=12772b67620de6cf06c368f57fa3eb6e128b1ca3'/>
<id>urn:sha1:12772b67620de6cf06c368f57fa3eb6e128b1ca3</id>
<content type='text'>
Without proper quoting the DEFAULT_IFS was getting set incorrectly,
which was causing problems with the storage of some variables later in
the script.  Quoting fixes the problem.
</content>
</entry>
<entry>
<title>configure: add help note about gmime version</title>
<updated>2012-05-26T00:40:55Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2012-05-23T18:38:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=fae97b1013a18ad960aa0cd413154783409f310d'/>
<id>urn:sha1:fae97b1013a18ad960aa0cd413154783409f310d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>configure: change gmime version in help message to 2.6</title>
<updated>2012-04-05T11:01:32Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2012-04-05T11:01:32Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6acd61dad91cb1b5c43261a3c6cf7583ecf16f13'/>
<id>urn:sha1:6acd61dad91cb1b5c43261a3c6cf7583ecf16f13</id>
<content type='text'>
Since GMime 2.6 is now the stable version upstream, and probably the
most tested by notmuch developers, it makes sense to suggest that to
users to install.
</content>
</entry>
<entry>
<title>configure: print info about required gmime 2.4 or 2.6 versions</title>
<updated>2012-04-05T10:53:04Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2012-03-21T19:18:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3c7d97c3c742fdf1b9a531ae639ce9ed6d4f5166'/>
<id>urn:sha1:3c7d97c3c742fdf1b9a531ae639ce9ed6d4f5166</id>
<content type='text'>
In case required gmime (2.4 or 2.6) version if not found print information
about both alternatives (and currently minimal 2.6 version that is needed).
</content>
</entry>
<entry>
<title>configure: add empty line after each missing component message</title>
<updated>2012-04-05T10:50:51Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2012-03-20T22:16:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e8138c522b386e4e7f6d3c57e62e6a185aaad336'/>
<id>urn:sha1:e8138c522b386e4e7f6d3c57e62e6a185aaad336</id>
<content type='text'>
Currently whenever message about missing GMime, Glib or talloc is
printed the message is 2 lines, component info and its http location
in next line. In the future the amount of lines will vary. To ease
reading in these cases newline is added after each message.
</content>
</entry>
</feed>
