<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/Makefile.global, branch 0.30_rc3</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.30_rc3</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.30_rc3'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2020-06-27T00:48:56Z</updated>
<entry>
<title>Makefile.global: drop -std=gnu99. C11 (or later) compiler required</title>
<updated>2020-06-27T00:48:56Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2020-06-24T20:11:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=751f6109225ccbe9a9008a2ff9381e4abfb4f71d'/>
<id>urn:sha1:751f6109225ccbe9a9008a2ff9381e4abfb4f71d</id>
<content type='text'>
Since October 2018 building notmuch has actually required compiler
that knows C11.

Also this -std=gnu99 was not used in code compiled by configure,
so in theory this could have caused problems...

...but no related reports have been sent, perhaps ever.

Both gcc and clang has been shipping compilers supporting C11
(or later) by default for more than four years now.

Therefore, just dropping -std=gnu99 (and not checking C11
compatibility for now, for simplicity) is easiest to do,
and removes inconsistency between configure and build time
compilations.
</content>
</entry>
<entry>
<title>release: use xz compression</title>
<updated>2019-03-27T20:59:40Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-03-19T10:08:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4bfbd5baa1e754e18d58dd6b8052a8072c0bfc2f'/>
<id>urn:sha1:4bfbd5baa1e754e18d58dd6b8052a8072c0bfc2f</id>
<content type='text'>
This produces tarballs that are roughly 30% smaller.
</content>
</entry>
<entry>
<title>build: Rename GPG_FILE to DETACHED_SIG_FILE</title>
<updated>2019-03-27T20:54:12Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-03-23T12:35:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1f82039e0da1adf078559ef9bf80e2b47858a607'/>
<id>urn:sha1:1f82039e0da1adf078559ef9bf80e2b47858a607</id>
<content type='text'>
This is just a semantic cleanup -- we have multiple files that are
OpenPGP signatures.  And while we're probably making signatures with
GnuPG, they can be verified with any OpenPGP implementation, so "GPG_"
is arguably both not specific enough, and overly-specific.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>build: distribute signed sha256sums</title>
<updated>2019-03-27T20:53:41Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-03-23T12:35:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=01f9c71312937011c4474688d3d1dd64c14731fb'/>
<id>urn:sha1:01f9c71312937011c4474688d3d1dd64c14731fb</id>
<content type='text'>
Distribute clearsigned sha256sum file in addition to the detached
signature.

Verifies that use the sha256sum ensure that the thing signed includes
the name of the tarball. This defends the verifier by default against
a freeze, rollback, or project substitution attack.

A verifier can use something like the following (as expressed in
bash):

      set -o pipefail
      wget https://notmuchmail.org/releases/notmuch-$VERSION.tar.gz{,.sha256.asc}
      gpgv --keyring ./notmuch-signers.pgp --output - notmuch-$VERSION.tar.gz.sha256.asc | sha256sum -c -

See id:87r2b8w956.fsf@fifthhorseman.net and other messages in that
thread for discussion.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>build: sign tarball instead of sha256sum</title>
<updated>2019-03-12T01:28:11Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-02-13T02:17:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b8a8dbed91d16299a8768646fb6f18181f31ec40'/>
<id>urn:sha1:b8a8dbed91d16299a8768646fb6f18181f31ec40</id>
<content type='text'>
Adam Majer pointed out in [1] the way were signing releases was
unusual. Neither Carl nor I could think of a good reason for
explicitely signing the checksum (internally of course that's what GPG
is going anyway).

[1] mid:b3fd556d-c346-7af9-a7a2-13b0f3235071@suse.de
</content>
</entry>
<entry>
<title>rename libutil.a to libnotmuch_util.a</title>
<updated>2017-03-19T00:37:43Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-03-14T11:10:07Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c39f6361d0798aa8d0dcd0b91f6b86ab9dc21c75'/>
<id>urn:sha1:c39f6361d0798aa8d0dcd0b91f6b86ab9dc21c75</id>
<content type='text'>
Apparently some systems (MacOS?) have a system library called libutil
and the name conflict causes problems. Since this library is quite
notmuch specific, rename it to something less generic.
</content>
</entry>
<entry>
<title>build: use sha256sum instead of sha1sum to sign releases</title>
<updated>2017-03-02T21:31:15Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-03-02T00:44:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=914c4db1f2cf5b19100b42a8e3ea62d000a9b642'/>
<id>urn:sha1:914c4db1f2cf5b19100b42a8e3ea62d000a9b642</id>
<content type='text'>
</content>
</entry>
<entry>
<title>build/emacs: add target to create elpa package</title>
<updated>2016-11-26T11:57:58Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-11-19T17:44:29Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=10f8c5d205d5398bb86809bf8e7958038ba3b6fe'/>
<id>urn:sha1:10f8c5d205d5398bb86809bf8e7958038ba3b6fe</id>
<content type='text'>
This package can be created without emacs, but will only be usable in
versions of emacs supporting package.el
</content>
</entry>
<entry>
<title>build: Move variable definitions to Makefile.global</title>
<updated>2016-11-26T11:46:42Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-11-19T17:44:28Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=46a47f06a628c7025246da040fa9ab6301c49313'/>
<id>urn:sha1:46a47f06a628c7025246da040fa9ab6301c49313</id>
<content type='text'>
I noticed when trying to use VERSION (and derived variables) in a
subdirectory that the top level Makefile.local needed to be included
first. But according to c10085c77b407d9ea704f8b4f9e0a805f63e72cb it
actually needs to be last. To break this conflict, move the variables
definitions into a new Makefile.global.
</content>
</entry>
</feed>
