GNU bug report logs - #25939
[PATCH] gnu: neomutt: Configure with "kyotocabinet".

Previous Next

Package: guix-patches;

Reported by: contact.ng0 <at> cryptolab.net

Date: Thu, 2 Mar 2017 21:13:01 UTC

Severity: normal

Tags: patch

Done: ng0 <contact.ng0 <at> cryptolab.net>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: ng0 <contact.ng0 <at> cryptolab.net>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#25939: closed ([PATCH] gnu: neomutt: Configure with
 "kyotocabinet".)
Date: Fri, 17 Mar 2017 17:47:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Fri, 17 Mar 2017 17:45:52 +0000
with message-id <20170317174552.m3bqlrav2ov742wx <at> abyayala>
and subject line Re: bug#25939: Acknowledgement ([PATCH] gnu: neomutt: Configure with "kyotocabinet".)
has caused the debbugs.gnu.org bug report #25939,
regarding [PATCH] gnu: neomutt: Configure with "kyotocabinet".
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
25939: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=25939
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: contact.ng0 <at> cryptolab.net
To: guix-patches <at> gnu.org
Cc: ng0 <contact.ng0 <at> cryptolab.net>
Subject: [PATCH] gnu: neomutt: Configure with "kyotocabinet".
Date: Thu,  2 Mar 2017 21:11:25 +0000
From: ng0 <contact.ng0 <at> cryptolab.net>

* gnu/packages/mail.scm (neomutt)[arguments]: Add "--with-kyotocabinet"
to configure-flags.
---
 gnu/packages/mail.scm | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gnu/packages/mail.scm b/gnu/packages/mail.scm
index ee82a1b8b..af1763b16 100644
--- a/gnu/packages/mail.scm
+++ b/gnu/packages/mail.scm
@@ -269,6 +269,7 @@ operating systems.")
        ("gdbm" ,gdbm)
        ("lmdb" ,lmdb)
        ("tokyocabinet" ,tokyocabinet)
+       ("kyotocabinet" ,kyotocabinet)
        ("gpgme" ,gpgme)
        ("ncurses" ,ncurses)
        ("gnutls" ,gnutls)
@@ -293,6 +294,7 @@ operating systems.")
              ;; database, implies header caching
              ;; neomutt supports building multiple backends
              "--with-tokyocabinet"
+             "--with-kyotocabinet"
              "--without-qdbm"
              "--without-bdb"
              "--with-lmdb"
-- 
2.12.0



[Message part 3 (message/rfc822, inline)]
From: ng0 <contact.ng0 <at> cryptolab.net>
To: Kei Kebreau <kei <at> openmailbox.org>
Cc: 25939-done <at> debbugs.gnu.org, Leo Famulari <leo <at> famulari.name>
Subject: Re: bug#25939: Acknowledgement ([PATCH] gnu: neomutt: Configure with
 "kyotocabinet".)
Date: Fri, 17 Mar 2017 17:45:52 +0000
Kei Kebreau transcribed 2.3K bytes:
> ng0 <contact.ng0 <at> cryptolab.net> writes:
> 
> > On 17-03-02 17:01:36, Leo Famulari wrote:
> >> On Thu, Mar 02, 2017 at 09:31:54PM +0000, ng0 wrote:
> >> > In the last patch which added tokyocabinet and its support to neomutt, I
> >> > did not know that neomutt has support for kyotocabinet which is a
> >> > separate database from tokyocabinet but kyotocabinet is the currently
> >> > developed/recommended database (by the database upstream).
> >> > 
> >> > Should we add this in addition or drop tokyocabinet in favor of adding
> >> > kyotocabinet ? I'm okay with just adding it.
> >> 
> >> Sorry, I replied to the patch before seeing this message. If
> >> tokyocabinet is unmaintained or superseded by kyotocabinet, then let's
> >> just remove it from neomutt.
> >> 
> >> 
> >> 
> >
> > No problem, I've only realized it after the patch was merged in. After
> > all the patch includes not only the tokyodb.
> > I'd read the database website and leave it up to someone else as a
> > second opinion what's the best course of action here.
> > I only knew of kyotocabinet before I found tokyo and read as tokyo as
> > the work which happened before kyotocabinet.
> 
> FYI, I committed the patch a little while ago. I decided to remove
> tokyocabinet, as kyotocabinet seems to be its successor. You may close
> the bug if you feel it has been addressed satisfactorily.


I noticed it (thanks :) ). I just did not know this was still open. I
think you may close bugs (NNNNN-close <at> debbugs.gnu.org) after you have
pushed them. If there are questions, they can still be addressed in the
closed bug and reopened.


This bug report was last modified 8 years and 72 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.