The current situation with nvidia-drivers is confusing. When the "gtk" USE flag is enabled, it pulls media-video/nvidia-settings as a dependency. And the result is: http://i50.tinypic.com/ml1p2g.png and two binaries that do the same thing: /usr/bin/nvidia-settings /opt/bin/nvidia-settings Also, nvidia-settings and nvidia-drivers are almost always out of sync when nvidia-drivers gets bumped because nvidia-settings doesn't. I propose that the nvidia-drivers ebuild should not pull nvidia-settings as a dependency (not even optionally through a USE flag), and users who need to develop applications using NVCtrlLib (nvidia-settings provides header files and libXNVCtrl.a) should emerge it on their own. It's obvious that users developing with NVCtrlLib know what they need. For the vast majority of users, NVCtrlLib headers and the static library are not needed, therefore nvidia-drivers should not depend on it; installing it serves no purpose whatsoever.
Oops, I'm sorry. I had not synced my tree yet, and now that I did I saw that nvidia-drivers-295.49 actually dropped that dependency! Wow, quite a coincidence :-/ Sorry for the noise. Closing as INVALID.
