Version: 3.2.1 (using KDE KDE 3.4.1) Installed from: Gentoo Packages Compiler: 3.4.4 OS: Linux i'm using gentoo ebuilds for kdevelop. i have a /usr/kdevbdb/ directory with lots of db stuff. i opened this bug: http://bugs.gentoo.org/show_bug.cgi?id=100476 but they told me it's kdevelop "bug" and not gentoo ebuild. why a separate directory? isn't it more clean to merge with /usr as root (ok...i know it depends on --prefix too..)
kdevelop ships with its own version of bdb that's known to work with code completion. installing it in the same --prefix as the rest of kdevelop could possible clobber another bdb version, hence the extra directory
and to answer the question about it being needed: yes, it's needed, certain versions of bdb cause kdevelop to crash when trying to do code completion. this is the only fix for that.
i don't agree. 1) other db has the version number. ls /usr/bin/db*_* /usr/bin/db1_dump185* /usr/bin/db3_verify* /usr/bin/db4.2_archive* /usr/bin/db4_checkpoint* /usr/bin/db3_archive* /usr/bin/db4.1_archive* /usr/bin/db4.2_checkpoint* /usr/bin/db4_deadlock* /usr/bin/db3_checkpoint* /usr/bin/db4.1_checkpoint* /usr/bin/db4.2_deadlock* /usr/bin/db4_dump* /usr/bin/db3_deadlock* /usr/bin/db4.1_deadlock* /usr/bin/db4.2_dump* /usr/bin/db4_load* /usr/bin/db3_dump* /usr/bin/db4.1_dump* /usr/bin/db4.2_load* /usr/bin/db4_printlog* /usr/bin/db3_dump185* /usr/bin/db4.1_load* /usr/bin/db4.2_printlog* /usr/bin/db4_recover* /usr/bin/db3_load* /usr/bin/db4.1_printlog* /usr/bin/db4.2_recover* /usr/bin/db4_stat* /usr/bin/db3_printlog* /usr/bin/db4.1_recover* /usr/bin/db4.2_stat* /usr/bin/db4_upgrade* /usr/bin/db3_recover* /usr/bin/db4.1_stat* /usr/bin/db4.2_upgrade* /usr/bin/db4_verify* /usr/bin/db3_stat* /usr/bin/db4.1_upgrade* /usr/bin/db4.2_verify* /usr/bin/db3_upgrade* /usr/bin/db4.1_verify* /usr/bin/db4_archive* i have installed db 1, 3 and 4. lots of versions. kdev db has db_* so problem is already bypassed. 2) if not, you just need to add a suffix or a prefix.. dunno somethign like dbkdev_upgrade and so on.. or kdb_upgrade there are so many possibilities 3) ideal fix would be make it work with normal db, of course, but if you did that trick probably you had problems with that.
KDevelop _WILL_ crash with if compiled against the wrong version of bdb. this is our fix for it. don't tell us how to write our software.
maybe you read too fast this bug report. you answered, in a bad way, to the 3) point. if you read better it you see: " ideal fix", "if you did that trick probably you had problems". you completly discarded points 1) and 2) that are a fix for install path, and for you crash problem. i didn't tell how to write software....i simply did a report with a simple suggestion. if you don't want report, what's the idea behind bugzilla?
> 1) other db has the version number. This is not the case in my distro. > 2) if not, you just need to add a suffix or a prefix.. I don't think we want to install it into the location where it can be used. This stuff is intimate to KDevelop ;) > 3) ideal fix would be make it work with normal db, of course, but if you did > that trick probably you had problems with that. Yep, crashes. Anyway, let's leave this bug closed because in KDevelop 4 we'll probably use another backend and not bdb so this will be automatically resolved.