--- Begin Message ---
|
Subject: |
[PATCH] gnu: neomutt: Configure with "kyotocabinet". |
|
Date: |
Thu, 2 Mar 2017 21:11:25 +0000 |
From: ng0 <address@hidden>
* 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
--- End Message ---
--- Begin Message ---
|
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 <address@hidden> 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 (address@hidden) after you have
pushed them. If there are questions, they can still be addressed in the
closed bug and reopened.
--- End Message ---