Summary: | k3b / kdesu problem after update to kde 3.5 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Wernfried Haas (RETIRED) <amne> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | rockoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Wernfried Haas (RETIRED)
2006-07-28 04:36:38 UTC
Well, KDE was never meant to be run with multiple versions side by side, so you noticed one of the problematic issues, a runtime dependency of another slotted version that isn't in path. A possible workaround would be to move each kde_binary_foo to kde_binary_foo-binary and create for each a kde_binary_foo script that calls kde_binary_foo-binary with its environment. Messy? Yes. :) Running multiple KDE versions is good for testing and eases migration, because (most) applications remain functional while rebuilding, but you should really do that and if you keep the older KDE version, do so only for development/compatibility tests. revdep-rebuild --library /usr/kde/3.4/lib/libkdecore.so.4 should do it in this case. I don't think we will ever do something about it. It's about time to remove KDE 3.4 from the tree anyways (imho). |