| 1 |
Hi All, |
| 2 |
|
| 3 |
A mutt update today complained about which database to use for hcache: |
| 4 |
|
| 5 |
!!! Problem resolving dependencies for mail-client/mutt from @selected |
| 6 |
.. done! |
| 7 |
|
| 8 |
!!! The ebuild selected to satisfy "mail-client/mutt" has unmet requirements. |
| 9 |
- mail-client/mutt-1.9.4-r1::gentoo USE="crypt gdbm gpg hcache imap lmdb mbox |
| 10 |
nls nntp pop sasl smime smtp ssl -berkdb -debug -doc -gnutls -gpgme -idn - |
| 11 |
kerberos -libressl -notmuch -pgp_classic (-prefix) -qdbm (-selinux) -slang - |
| 12 |
smime_classic -tokyocabinet -vanilla" ABI_X86="(64)" |
| 13 |
|
| 14 |
The following REQUIRED_USE flag constraints are unsatisfied: |
| 15 |
hcache? ( exactly-one-of ( berkdb gdbm lmdb qdbm tokyocabinet ) ) |
| 16 |
|
| 17 |
The above constraints are a subset of the following complete expression: |
| 18 |
hcache? ( exactly-one-of ( berkdb gdbm lmdb qdbm tokyocabinet ) ) imap? ( |
| 19 |
ssl ) pop? ( ssl ) nntp? ( ssl ) smime? ( ssl !gnutls ) smime_classic? ( ssl ! |
| 20 |
gnutls ) smtp? ( ssl ) sasl? ( any-of ( imap pop smtp nntp ) ) kerberos? ( |
| 21 |
any-of ( imap pop smtp nntp ) ) |
| 22 |
|
| 23 |
So far I had been using gdbm, but I now see that emerge also added lmdb. |
| 24 |
Which one is best to use? What have you chosen? |
| 25 |
|
| 26 |
-- |
| 27 |
Regards, |
| 28 |
Mick |
Archives