Hello. mail/neomutt do have lmdb and tokyocabinet header-cache options ON by default. Please, consider kyotokabinet to be default instead of tokyocabinet, since even tokyocabinet dev recommends to use kyotocabinet instead: http://fallabs.com/tokyocabinet/ I can bring a patch. Thanks!
Please attach a patch. Thanks!
Created attachment 186386 [details] Updating mail/neomutt port. * Updating to 20170912 * Setting KYOTOCABINET as default header-cache instead of TOKYOCABINET * Fix minor warning about USE_GITHUB appearing before USE in the port.
I'd already updated the HEAD port with 20170912 and the portlint warning.
Created attachment 186389 [details] Setting KYOTOCABINET as default header-cache instead of TOKYOKABINET * Setting KYOTOCABINET as default header-cache instead of TOKYOKABINET
I forgot to update the ports tree. Sorry about that. Thanks!
I was reluctant into doing that. Because of kyotocabinet being GPLv3 (note the missing L even if there is an explicit link exception). The goal in the default set of options on is to have the fastest database for header cache: lmdb and another one which is safe over NFS (lmdb is not safe over NFS) and tokyocabinet was chosen because among the safe database format it is the faster which a license allowing linking by default without being controversial. Is there any end user visible improvements to add kyotocabinet? It is a "big" new dependency: Flat size : 13.1MiB Pkg size : 1.37MiB
I do understand your concern, I had not paid attention to the kyotocabinet license. About the end user improvements, I was not using tokyocabinet before and currently I do not have a high amount of e-mails to say anything about that with some "authority". So, I totally agree with you. Thanks!
=> So, I totally agree with you. means that we can close here?