-devel: should add Requires: xorg-x11-proto-devel Requires: libX11-devel for usage of X11/X.h and X11/Xlib.h, repectively, in it's own installed headers. These are the first ones I've found by casual inspection, there may be more. You may want to add whatever(??) owns libICE.so, since kdelibs' .la files include references to it, and libXt-devel (since many/most kde apps' default ./configure test for the presence ot X libs looks for libXt.so)
I see that libICE/libX11 is picked up by qt-devel, though arguably, libX11 should be here in kdelibs too, since it contains direct references to X11/Xlib.h
(In reply to comment #0) > and libXt-devel (since many/most kde apps' default > ./configure test for the presence ot X libs looks for libXt.so) FWIW, I think this alone is not a reason to make kdelibs-devel pull libXt-devel in. If the apps use it directly (for configure tests or whatever), they should have a build dependency on it.
Re: comment #2: No, the apps don't use libXt directly, but kde's *generic* configure test for X includes and X libraries look for X11/Intrinsic.h and libXt respectively. If libXt-devel isn't added to kdelibs-devel's Req's, then (almost?) *every* kde application will need: BuildRequires: libXt-devel just to build, even though they don't use it. OTOH, it's arguable that kde's generic test for the presence of X headers/libs is wrong/unnecesssary.
it seems qt needs libXt-devel for building, those requires should be added in qt-devel. Many thanks for your reports.
Don't forget kdelibs-devel should have Requires: xorg-x11-proto-devel libX11-devel regardless of qt-devel's situation.