according to what I've read kdevelop 3.4 (maybe other versions?) should be able to build against kdelibs-3.5.6 which is what I'm running on my system. it seems to build ok... unless I use the --deep option which seems to give problems... ('ebuild', '/', 'kde-base/kdelibs-3.5.5-r9', 'merge') pulled in by ('ebuild', '/', 'kde-base/kdesdk-kioslaves-3.5.5', 'nomerge') ('ebuild', '/', 'kde-base/kdelibs-3.5.6-r3', 'nomerge') pulled in by ('ebuild', '/', 'dev-util/kdevelop-3.4.0-r2', 'merge') I'm not sure why this seems to think it needs old 3.5.5 dependancies. when it should (and probably does) run fine on 3.5.6 dependancies. I'm sorry if this isn't a bug. just from what I've read seems like it should work. Reproducible: Always
kdesdk-kioslaves depends on kdelibs 3.5.5 kdevelop depends on 3.5.6
(In reply to comment #1) > kdesdk-kioslaves depends on kdelibs 3.5.5 > kdevelop depends on 3.5.6 > ok I can see that but why does this only seem to occur when I try to merge kdevelop (or have it merged and try to do a --deep update on world). I do not have this problem unless I try to merge it. i have worked out almost every other kde package that I used when I upgraded to 3.5.6 (to fix a kmail bug I was having).
Don't mix ~arch and arch for KDE parts, as seen above, it won't work.
(In reply to comment #3) > Don't mix ~arch and arch for KDE parts, as seen above, it won't work. > honestly I didn't realize I was. because I spent an entire evening clearing out kde programs I wasn't using. revdep-rebuild wasn't catching this, and neither was emerge -avuDN world. problems that can be cause by not having something in your world file I think... sorry aobut the invalid bug I realize my mistake here.
