Re: Can't compile notmuch-delivery

diff --git a/a9/3e7a7d1ef7d889656b72faa4c447dea847c935 b/a9/3e7a7d1ef7d889656b72faa4c447dea847c935
new file mode 100644 (file)
index 0000000..8c793fd
--- /dev/null
+++ b/a9/3e7a7d1ef7d889656b72faa4c447dea847c935
@@ -0,0 +1,106 @@
+Return-Path: <bremner@unb.ca>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id CEE02431FB6\r
+       for <notmuch@notmuchmail.org>; Fri,  1 Jun 2012 11:17:52 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.01\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.01 tagged_above=-999 required=5\r
+       tests=[T_MIME_NO_TEXT=0.01] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id UljcU39biuiF for <notmuch@notmuchmail.org>;\r
+       Fri,  1 Jun 2012 11:17:52 -0700 (PDT)\r
+Received: from tesseract.cs.unb.ca (tesseract.cs.unb.ca [131.202.240.238])\r
+       (using TLSv1 with cipher AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 5F5B8431FAF\r
+       for <notmuch@notmuchmail.org>; Fri,  1 Jun 2012 11:17:52 -0700 (PDT)\r
+Received: from fctnnbsc30w-156034089108.dhcp-dynamic.fibreop.nb.bellaliant.net\r
+       ([156.34.89.108] helo=zancas.localnet)\r
+       by tesseract.cs.unb.ca with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32)\r
+       (Exim 4.72) (envelope-from <bremner@unb.ca>)\r
+       id 1SaWPx-0006eG-QY; Fri, 01 Jun 2012 15:17:46 -0300\r
+Received: from bremner by zancas.localnet with local (Exim 4.77)\r
+       (envelope-from <bremner@unb.ca>)\r
+       id 1SaWPs-00035u-Fo; Fri, 01 Jun 2012 15:17:40 -0300\r
+From: David Bremner <david@tethera.net>\r
+To: Jameson Graef Rollins <jrollins@finestructure.net>,\r
+       Felipe Contreras <felipe.contreras@gmail.com>,\r
+       Tomi Ollila <tomi.ollila@iki.fi>\r
+Subject: Re: Can't compile notmuch-delivery\r
+In-Reply-To: <87sjefufub.fsf@servo.finestructure.net>\r
+References: <20120531214259.GA18272@desktop>\r
+       <m2pq9jo7jf.fsf@guru.guru-group.fi>\r
+       <CAMP44s0vvEDLd2DceFraNpqyMrX2A+=zkV6W=ABatZs52FNo5Q@mail.gmail.com>\r
+       <87lik7171d.fsf@zancas.localnet>\r
+       <87sjefufub.fsf@servo.finestructure.net>\r
+User-Agent: Notmuch/0.13.1 (http://notmuchmail.org) Emacs/23.4.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Fri, 01 Jun 2012 15:17:26 -0300\r
+Message-ID: <874nqu28y1.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha1; protocol="application/pgp-signature"\r
+X-Spam_bar: -\r
+Cc: Ali Polatel <alip@exherbo.org>, notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Fri, 01 Jun 2012 18:17:53 -0000\r
+\r
+--=-=-=\r
+\r
+Jameson Graef Rollins <jrollins@finestructure.net> writes:\r
+\r
+> I don't know, but this is one of the reasons I'm against having\r
+> "contrib" stuff in the notmuch repo.  If it's not part of the stuff\r
+> we're willing to release in source tarballs or binary packages then it\r
+> should probably be in a separate repo.\r
+\r
+Just to be clear, ./contrib currently is in the source tarballs, and at\r
+least notmuch-mutt is included in a binary package for debian.\r
+\r
+I don't disagree that status is kindof odd, but I don't see the stuff in\r
+contrib as being that different in practice from the bindings. In both\r
+cases we have had incidences of bitrot. The python bindings are\r
+currently not a problem, but both the ruby and go bindings stopped\r
+working at all recently.\r
+\r
+Ideally everything would be automated testable, but this is not the case\r
+right now. Somebody (Jani?) mentioned on irc that having things\r
+integrated into the toplevel build system (presumably as an optional\r
+target) would be a start.\r
+\r
+I guess we could have some protocol where a "subsystem maintainer" has\r
+to sign off before the release, or we just don't export it to the\r
+release tarball. But then, it would slow the release process down,\r
+especially for point (bugfix) release.\r
+\r
+d\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.12 (GNU/Linux)\r
+\r
+iJwEAQECAAYFAk/JBzcACgkQTiiN/0Um85l97wQAiaTsc+8t9B03vTS9vW/I9Q/J\r
+0gpK2hkzI7CMUvUSlXbVov5eGf2jZYsjXAiI3XXgUPF32hahTdBRhpaK95BbKhcB\r
+qhZj5uPeET1hJCXVWPc8uxETaQuHWJJgp2+hCOEdPz4NofCSqsh6MFCHHChlAfI0\r
+XG/Ux15VkrKjGHPVNAc=\r
+=EVO1\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r