On 17-02-11 21:07:39, contact....@cryptolab.net wrote: > [PATCH 1/2] gnu: Add tokyocabinet. > > Pretty straight forward, just adds the database. > > [PATCH 2/2] gnu: neomutt: Configure with 'lmdb' and 'tokyocabinet'. > > Adds the lmdb and tokyocabinet as two more choices of database backends to > neomutt. This is not a problem for neomutt as multiple backends can be > handled at the same time. >
"But why did you pick these two and not others?" I've read a comment in the FreeBSD bug/patch tracker where they judged that these are the two fastest databases to be used for this job. Do we need the original one we currently have? I don't know who uses neomutt already, but I don't feel good with breaking peoples software. "Oops, now your database is no longer built into our version of the application" ... hm. I think my choice to stick with the 3 DBs is right and it doesn't add much. guix size: * for neomutt as it is currently: store item total self /gnu/store/7zvsqc6pr6yalalwbsv88hzx2laxbkxn-neomutt-20170113 379.7 4.9 1.3% total: 379.7 MiB store item total self /gnu/store/0f4qjgd4nr53r5xsg6di9nxprzg26kdd-neomutt-20170113 384.7 4.9 1.3% total: 384.7 MiB I skipped the other store items, but the difference is minimal. -- ng0 -- https://www.inventati.org/patternsinthechaos/
