Re: notmuch as a shared object aka library knigge

diff --git a/26/13a231723c66b18a7c3959916d0af835ba022c b/26/13a231723c66b18a7c3959916d0af835ba022c
new file mode 100644 (file)
index 0000000..809aa82
--- /dev/null
+++ b/26/13a231723c66b18a7c3959916d0af835ba022c
@@ -0,0 +1,101 @@
+Return-Path: <teythoon@jade-hamburg.de>\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 EDFBF431FBC\r
+       for <notmuch@notmuchmail.org>; Thu, 23 Feb 2012 14:22:06 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       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 5VNbAshjhK0I for <notmuch@notmuchmail.org>;\r
+       Thu, 23 Feb 2012 14:22:05 -0800 (PST)\r
+Received: from mail.cryptobitch.de (cryptobitch.de [88.198.7.68])\r
+       (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 119FE431FAE\r
+       for <notmuch@notmuchmail.org>; Thu, 23 Feb 2012 14:22:05 -0800 (PST)\r
+Received: from mail.jade-hamburg.de (unknown [85.183.11.228])\r
+       (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by mail.cryptobitch.de (Postfix) with ESMTPSA id 8CC20530E40\r
+       for <notmuch@notmuchmail.org>; Thu, 23 Feb 2012 23:22:03 +0100 (CET)\r
+Received: by mail.jade-hamburg.de (Postfix, from userid 401)\r
+       id D42CFDF2A9; Thu, 23 Feb 2012 23:22:02 +0100 (CET)\r
+Received: from thinkbox.jade-hamburg.de\r
+       (dslb-088-075-032-221.pools.arcor-ip.net [88.75.32.221])\r
+       (using TLSv1 with cipher AES256-SHA (256/256 bits))\r
+       (No client certificate requested) (Authenticated sender: teythoon)\r
+       by mail.jade-hamburg.de (Postfix) with ESMTPSA id 14185DF2A7\r
+       for <notmuch@notmuchmail.org>; Thu, 23 Feb 2012 23:22:01 +0100 (CET)\r
+Received: from teythoon by thinkbox.jade-hamburg.de with local (Exim 4.77)\r
+       (envelope-from <teythoon@thinkbox.jade-hamburg.de>)\r
+       id 1S0h32-0006XQ-Td\r
+       for notmuch@notmuchmail.org; Thu, 23 Feb 2012 23:22:00 +0100\r
+Content-Type: text/plain; charset="utf-8"\r
+MIME-Version: 1.0\r
+Content-Transfer-Encoding: quoted-printable\r
+From: Justus Winter <4winter@informatik.uni-hamburg.de>\r
+User-Agent: alot/0.21+\r
+To: notmuch mailing list <notmuch@notmuchmail.org>\r
+References: <20120221002921.8534.57091@thinkbox.jade-hamburg.de>\r
+       <20120221155312.GB30513@mit.edu>\r
+       <20120222151745.4213.93513@thinkbox.jade-hamburg.de>\r
+In-Reply-To: <20120222151745.4213.93513@thinkbox.jade-hamburg.de>\r
+Message-ID: <20120223222200.17796.11840@thinkbox.jade-hamburg.de>\r
+Subject: Re: notmuch as a shared object aka library knigge\r
+Date: Thu, 23 Feb 2012 23:22:00 +0100\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: Thu, 23 Feb 2012 22:22:07 -0000\r
+\r
+Quoting Justus Winter (2012-02-22 16:17:45)\r
+>Quoting Austin Clements (2012-02-21 16:53:12)\r
+>>As always, patches welcome!\r
+>\r
+>Well, hacking on c code in my free time is not my idea of fun and I'm\r
+>not familiar with the code base, so I'd appreciate it if someone who\r
+>is in a better position to whip up a patch would step up and do so.\r
+\r
+That wasn't meant to sound as harsh as it probably did. I seriously\r
+hope that someone is around who enjoys to hack on the c/c++ part of\r
+the library and is willing fix problems in it.\r
+\r
+I've got a lot of ideas how to improve the python bindings and have\r
+been refactoring it in the past few days. And while doing so I came\r
+across a few problems in the library, one of which was so easy to fix\r
+that I did just that.\r
+\r
+And I worked around the two functions (that I know of) that call\r
+exit(3) by conditionally raising exceptions in the python bindings,\r
+but this is only meant as a intermediate fix, a hack that should be\r
+removed as soon as the library is fixed.\r
+\r
+But most of those problems require api changes and some kind of idea\r
+on how to do this in a consistent and extensible way while hopefully\r
+providing a smooth transition to the new api. And I don't feel that\r
+I'm in a good position to do this (I know next to nothing about symbol\r
+versions and linker magic) so I mentioned the problems and asked for\r
+help on this issue.\r
+\r
+Btw, I think that we can keep the python api stable even if we change\r
+the underlying library. So if there isn't actually anyone who directly\r
+links against libnotmuch (maybe the mutt fork does?) we may not even\r
+worry so much about api stability of libnotmuch.\r
+\r
+Happy hacking,\r
+Justus\r