<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/Makefile.local, branch 0.20</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.20</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.20'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2015-03-08T07:30:36Z</updated>
<entry>
<title>python: replace hardcoding of SONAME version</title>
<updated>2015-03-08T07:30:36Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-03-07T07:31:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=aed5ec4350809aef34ae8290f8eda2069444b171'/>
<id>urn:sha1:aed5ec4350809aef34ae8290f8eda2069444b171</id>
<content type='text'>
Failing to update this string in globals.py causes failures when the
SONAME changes.  In order to hopefully reduce the number of such
errors, automate the process of setting the SONAME in the python
bindings.
</content>
</entry>
<entry>
<title>build: generate sh.config for feeding configure results to shell scripts</title>
<updated>2014-07-13T15:15:47Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2014-05-30T07:43:04Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=57540a1952460fe88817ad53dc32274543cf0514'/>
<id>urn:sha1:57540a1952460fe88817ad53dc32274543cf0514</id>
<content type='text'>
Only include the relevant information.

Amended by David Bremner:

	Use a prefix NOTMUCH_ to minimize collisions with other
	variables.
</content>
</entry>
<entry>
<title>build: check .git directory existence in srcdir (for out-of-tree builds)</title>
<updated>2014-07-09T23:24:28Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2014-05-06T19:35:28Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6721222ea8e3e8c0de15c5ae6f3ae0e388676c2a'/>
<id>urn:sha1:6721222ea8e3e8c0de15c5ae6f3ae0e388676c2a</id>
<content type='text'>
So that $(VERSION) and version.stamp uses the git-describe -based
version data instead of the content of `version' file.

For consistency also the git commands in Makefile[.local] target
`verify-no-dirty-code' uses the git --git-dir=$srcdir/.git ...
commands (inside ifeq($(IS_GIT),yes)). Attempting to make this
target outside of the tree will fail in any case.
</content>
</entry>
<entry>
<title>build: add dataclean</title>
<updated>2014-05-28T12:52:10Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-05-04T06:10:49Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=fe8cd90f97a078336612cd441a783096d6350564'/>
<id>urn:sha1:fe8cd90f97a078336612cd441a783096d6350564</id>
<content type='text'>
It turns out to be inconvenient to delete the downloaded datafiles with
distclean, so I propose a new target which does that instead.

The closest conventional target is 'maintainer-clean'; the difference
here is that having the original source tarball is not enough to
reconstruct these files.
</content>
</entry>
<entry>
<title>build: remove .tar.gz.tmp files in clean</title>
<updated>2014-05-28T12:51:51Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-05-04T06:10:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=18565743949174e28576a751ae18b90dcfc60c40'/>
<id>urn:sha1:18565743949174e28576a751ae18b90dcfc60c40</id>
<content type='text'>
Most people won't see these, but they annoy anyone running release
or pre-release targets.
</content>
</entry>
<entry>
<title>Merge branch 'release'</title>
<updated>2014-05-28T12:50:32Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-05-28T12:50:32Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=94064a6ba2f67005352915dc01c6eb0e19b761f9'/>
<id>urn:sha1:94064a6ba2f67005352915dc01c6eb0e19b761f9</id>
<content type='text'>
A point release is slowly being built on branch release. Merge those
changes into master.
</content>
</entry>
<entry>
<title>build: fix order of rpath</title>
<updated>2014-05-28T12:50:04Z</updated>
<author>
<name>Felipe Contreras</name>
<email>felipe.contreras@gmail.com</email>
</author>
<published>2014-05-12T02:22:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=90f9a5e65e8dab3fad0a60530d3ffc582f1b1a93'/>
<id>urn:sha1:90f9a5e65e8dab3fad0a60530d3ffc582f1b1a93</id>
<content type='text'>
In my system `pkg-config --libs talloc` returns
'Wl,-rpath,/usr/lib -ltalloc' (probably wrongly) which causes the final
LDFLAGS to be something like '-Wl,-rpath,/usr/lib
-Wl,-rpath,/opt/notmuch/lib', which causes the RUNPATH to be
'/usr/lib:/opt/notmuch/lib', so basically defeating the whole purpose of
RUNPATH.

I noticed this when my /opt/notmuch/bin/notmuch (0.17) started updating
the database after I updated the system (which updated the system's
notmuch). This shouldn't happen.

Let's move the RUNPATH flags before other external flags have a chance of
screwing the build.

Signed-off-by: Felipe Contreras &lt;felipe.contreras@gmail.com&gt;
</content>
</entry>
<entry>
<title>Merge tag '0.18_rc1'</title>
<updated>2014-05-03T23:32:05Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-05-03T23:32:05Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=21cb851a22f41e0b2a7c07dcbcc4f2dec20a0e3d'/>
<id>urn:sha1:21cb851a22f41e0b2a7c07dcbcc4f2dec20a0e3d</id>
<content type='text'>
notmuch 0.18~rc1 release
</content>
</entry>
<entry>
<title>build: use UPSTREAM_TAG and not VERSION to generate tarball</title>
<updated>2014-05-03T23:11:35Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-05-03T23:11:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=55354534953fd631ae1f51cf0f46732f00fde9c2'/>
<id>urn:sha1:55354534953fd631ae1f51cf0f46732f00fde9c2</id>
<content type='text'>
The latter can have "~" in it, which is not legal for a git tag.
</content>
</entry>
<entry>
<title>building from git: use --abbrev=7 for version string</title>
<updated>2014-04-24T05:01:05Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2014-04-22T15:19:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=bc64cdce289d84be2550c4fccb1f008d15eaeb0e'/>
<id>urn:sha1:bc64cdce289d84be2550c4fccb1f008d15eaeb0e</id>
<content type='text'>
Users may have set core.abbrev=n, where n != 7 in their git config
file(s) which would give them different than expected version strings
when building notmuch from git. This fixes the commit hash part of
version string to 7 hexadecimal values.
</content>
</entry>
</feed>
