The ebuild for app-misc/tracker-0.6.4 (and also 0.6.3) has an incorrect SQLite3 dependency, which causes Portage to give up on "emerge -uD world" with this error [1] if you have >=dev-db/sqlite-3.5* installed. If you have a look at tracker configure.ac [2], you'll see they require sqlite3 >= 3.4*, so the dep =dev-db/sqlite-3.4* in tracker ebuild is incorrect. Modifying it to ">=" solves this bug. [1] : dev-db/sqlite:3 ('ebuild', '/', 'dev-db/sqlite-3.4.2', 'merge') pulled in by ('ebuild', '/', 'app-misc/tracker-0.6.4', 'merge') ('installed', '/', 'dev-db/sqlite-3.5.3', 'nomerge') pulled in by ('installed', '/', 'dev-ruby/sqlite3-ruby-1.2.1', 'nomerge') ('installed', '/', 'net-news/liferea-1.4.9', 'nomerge') ('installed', '/', 'media-gfx/f-spot-0.4.0-r1', 'nomerge') (and 4 more) [2] : http://svn.gnome.org/viewvc/tracker/trunk/configure.ac?view=markup
Also, in the aforementioned ebuild we should check for "! built_with_use threadsafe" instead of "built_with_use nothreadsafe" to check use flags for dev-db/sqlite. These two fixes make tracker compile and run fine with dev-db/sqlite-3.5*.
Also in pkg_setup() part: built_with_use fpr poppler-bindings should first check if pdf support is in USE ... if use pdf && ! built_with_use 'app-text/poppler-bindings' 'gtk' ; then ...
The dep was not incorrect, it was there on purpose. There was a bug with sqlite 3.5 for a while though we never bothered to update the autoconf scripts. It seems that the fix did get into the release, so Ive re-enabled sqlite 3.5 as a valid provider. @pritt: thanks for the gtk catch, fixed as well.
