The gift-openft plugin needs to be built with support for berkeley db 3 or 4 on any machine that is to run as a search node. However, gift-openft's configure script fails to locate either version when both db3 and db4 are installed. Reproducible: Always Steps to Reproduce: 1. emerge /usr/portage/sys-libs/db/db-3.3.11.ebuild 2. emerge /usr/portage/sys-libs/db/db-4.1.25_p1-r3.ebuild 3. emerge gift-openft Actual Results: You'll notice that configure has this line near the end of its output: uze libdb...............: no I'm sure "uze" is a typo for "use", but anyway... Without libdb support, setting class=3 in OpenFT.conf will cause giftd to fail on startup with an error like: [23:17] *** GIFT-ERROR: OpenFT: dropping FT_NODE_SEARCH status due to lacking libdb support Expected Results: gift-openft's configure should find the latest version of db installed and use it. As a workaround, unmerging db4, emerging gift-openft, then re-emerging db (assuming you still want it) seems to have worked for me. It was suggested to me by the developer that the current poor performance of the OpenFT network is due in part to the lack of search nodes. Apparently, users who run search nodes also get better results... so it would be really nifty if we could get this to work. I know this bug is common to many ebuilds, and I've been trying in vain to patch it myself. I'd be pleased If someone could point me toward any docs on making ebuilds db4 friendly.
Is this still happening with gift-openft-0.2.1.3?
With the latest version of gift-openft in portage and with the libdb stuff installed, uze libdb...............: yes :)
btw, berkdb is now added to the USE flags to enable/disable becoming a node :)
