As of today this bug holds for libglade-java-2.12.2-r1.ebuild, libglade-java-2.12.6.ebuild and libglade-java-2.12.6-r1.ebuild. Steps to reproduce: USE="-gnome" emerge -pvDt libglade-java Actual results: Lots of gnome-specific libraries in the dependency tree. Expected results: No gnome-specific library in the dependency tree. Proposed fix: 1. Move libgnome-java to the gnome? (...) conditional block. 2. Use the pkg_setup() as in libglade-java-2.12.2-r1.ebuild, but add: use gnome || myflags="{$myflags} --without-gnome"
Sorry, that was src_compile(), not pkg_setup()
It's also missing libgtk-java (hard) dependency...
Created attachment 105472 [details, diff] ebuild patch this worked for me (both USE=gnome and -gnome) not sure if these extra libs are really needed tho. I've noticed another problem - these java dependencies don't get recorded into package.env :/
Oh yeah, such a mess. I spent 6 hours the other day trying to debug a one line m4 autoconf macro problem to make the old java-gnome build on Solaris. And people wonder why we're deep sixing it :) FWIW, for the new 4.0 bindings it is looking increasingly like it will be a single java-gnome source release, with a number of .jar and .so build products allowing distros to package them as individual files if they wish. AfC
(In reply to comment #3) > Created an attachment (id=105472) [edit] > ebuild patch > Patch committed. > this worked for me (both USE=gnome and -gnome) not sure if these extra libs are > really needed tho. > > I've noticed another problem - these java dependencies don't get recorded into > package.env :/ > Recording was fixed in bug 158249.
