DEPEND="app-arch/unzip >=x11-libs/gtk+-2.2 >=x11-libs/pango-1.2 >=dev-libs/libxml-1.8.15 mikmod? ( >=media-libs/libmikmod-3.1.10 ) esd? ( >=media-sound/esound-0.2.29 ) gnome? ( >=gnome-base/gnome-2.2 ) opengl? ( virtual/opengl ) oggvorbis? ( >=media-libs/libvorbis-1.0 )" RDEPEND="${DEPEND} nls? ( dev-util/intltool )" This should be in reverse.
Urmm, I'm pretty sure gtk/pango and such are compile time dependency's not runtime deps. Not sure about the rest though.
Well, that should read: RDEPEND="app-arch/unzip >=x11-libs/gtk+-2.2 >=x11-libs/pango-1.2 >=dev-libs/libxml-1.8.15 mikmod? ( >=media-libs/libmikmod-3.1.10 ) esd? ( >=media-sound/esound-0.2.29 ) gnome? ( >=gnome-base/gnome-2.2 ) opengl? ( virtual/opengl ) oggvorbis? ( >=media-libs/libvorbis-1.0 )" DEPEND="${RDEPEND} nls? ( dev-util/intltool )" To get it right, intltool is a build-time helper. And, there is a fair chance that "nls" USE flag isn't optional.
looking into this now...
DEPEND/RDEPEND fixed up. I just tested that the package emerges fine with USE=-nls because it sets the configure option '--disable-nls'.
the case I wonder about: what if USE="-nls" and intltool isn't installed? Does anything balk at that? (most systems have intltool anyhow, so its not a common case, even with USE="-nls" )
I unmerged intltool before testing -nls ;)