Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 0E0D4431FC7 for ; Sun, 28 Sep 2014 11:28:57 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MlSeJfCv7q4d for ; Sun, 28 Sep 2014 11:28:53 -0700 (PDT) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 9A82D431FAE for ; Sun, 28 Sep 2014 11:28:53 -0700 (PDT) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1XYJDD-0005fn-QG for notmuch@notmuchmail.org; Sun, 28 Sep 2014 15:28:47 -0300 Received: (nullmailer pid 31273 invoked by uid 1000); Sun, 28 Sep 2014 18:28:41 -0000 From: David Bremner To: notmuch@notmuchmail.org Subject: Date: Sun, 28 Sep 2014 20:28:16 +0200 Message-Id: <1411928899-29625-1-git-send-email-david@tethera.net> X-Mailer: git-send-email 2.1.0 In-Reply-To: <87iok8vog6.fsf@steelpick.2x.cz> References: <87iok8vog6.fsf@steelpick.2x.cz> X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 18:28:57 -0000 Here's one approach to keeping config information at the library level. IMHO, a key philosophical point is that this metadata is associated with a database, not with the library. Having every key map to a distinct file is arguably not as nice for humans to edit, but it avoids certain concurrency complications; e.g. glib can atomically write a keyfile (like we use for .notmuch-config), but that means e.g. the result of two concurrent updates to different keys is not a valid serialization. It won't be very efficient for huge numbers of keys, but for keeping some static metadata associated with a notmuch database, this should work ok. In addition to needing some polishing (documentation? what documentation?), this isn't actually used anywhere in notmuch.