Hi, I am going to add (in mutt) support for header caching by enabling the relative switch (--enable-hcache) during configuration.
The obvious advantage in Mutt when using header caching is that allows large remote mailboxes to be opened (much more) faster; as Mutt stores the (imap) headers in a local database. So Mutt has to be linked against a db application, i.e, qdbm, gdbm or db (one of the three), with qdbm to take precedence over the other two and gdbm over the Berkeleydb. So at first we need to introduce qdbm (1) in the dependencies list. Secondly, do we want to add this option by default? As a said it makes more sense when using Imap. But then we give support for Imap by default. I don't know if you aware (you are probably are, but just for the uniformed), google offers Imap support (which works quite well) in it's mail (gmail) implementation, so (Imap) will probably be popular in the near future. As you know by using Imap over POP, it gives you a number of advantages which makes it very attractive. Now, if you want to give precedence in one db application, you have to explicitly enable it and at the same time disable the other two, like: --without-qdbm --with-gdbm --without-bdb --without-qdbm --without-gdbm --with-bdb The default as you guessed is: --with-qdbm --without-gdbm --without-bdb And this I would like to use, because that is what Mutt developers recommend. Keep in mind that there were (some) reports when using db as a backend. And one more thing; currently Berkeleydb is not listed at the dependency list because is already installed in LFS. That is not a problem usually but in this occasion it might be (a problem), as the user doesn't get informed that he has a choice to use db instead of the other two. Anyway this is not going to be a problem if we follow the defaults. So, do we want to enable --enable-hcache by default? Does remind you of something? Yes its the same situation with links browser. If we don't enable it, please can you provide me with a sort summary of the above, in the "--enable-hcache" option that is going to be added in the commands explanations section? I have difficulties to express it in well written sort English. Thanks for listening, Ag. 1.http://qdbm.sourceforge.net/ -- http://wiki.linuxfromscratch.org/blfs/wiki/Hacking -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
