xterm-212-r2.ebuild has the following RDEPEND:
RDEPEND="|| ( ( x11-libs/libX11
unicode? ( x11-apps/luit ) )
Xaw3d? ( x11-libs/Xaw3d )
virtual/x11 doesn't pull in x11-apps/luit, so in effect it depends on luit only if virtual/x11 isn't installed and USE=unicode, instead of whenever USE=unicode.
It seems that unicode? ( x11-apps/luit ) should be brought out of the OR to the same level as Xaw3d.
The dependency is correct.
ANY kind of explanation would be appreciated.
The dependecy would be correct in my book if virtual/x11 pulls in luit - but it doesn't.
Then again, now I was explained elsewhere that putting it outside would break monolith installs.
As I now don't see other solution than adding it to virtual/x11 (with a USE=unicode perhaps, which wouldn't be good either) either, so closing it again.
Indeed, adding such specific stuff to the virtual/x11 dependencies is not the best idea. Feel free to file a bug that requests removing virtual/x11-7* from portage so that it doesn't break modular deps. The dependencies here are correct as they are, not an xterm ebuild bug.