The following ebuilds are found to have broken autotools handling, as they run libtoolize directly (they never should, instead they should call eautoreconf in autotools.eclass, read http://www.gentoo.org/proj/en/qa/autofailure.xml for more information): ./dev-java/libgtk-java/libgtk-java-2.8.3-r1.ebuild: libtoolize --force --copy || die "libtoolize failed" Please cleanup the ebuilds by asking for stable marking, removing obsolete ebuilds with no relevant keywords, or porting the fixes in newer versions (if presents) to properly handle autotools. Thanks, Diego
Let's get libgtk-java-2.8.7-r1.ebuild stable then... it's not exactly 30 days old but revbump from -r0 didn't change ebuild, just ensured everyone will get a minor change to java-gnome.eclass applied. Last arch please note you are the last so we can punt the old ebuilds.
On second thought, I will rather leave this to Betelgeuse to decide, as I don't understand java-gnome that much and I am not sure whether all 6 parts of it need to go stable together. Sorry for the spam.
libgtk-java 2.8.7 corresponds to GNOME 2.14 and was superceeded by libgtk-java 2.10.x. Furthermore, this is part of the old java-gnome bindings, which are no longer being maintained. AfC
But since we don't have that new ones in tree yet, I think it's best to stabilize what we have (and it's using java-gnome eclass unlike the current stables), no?
The old ones are _abandonded_. I am the maintainer (because it got dumped on me) of the old 2.x series and the author (because I decided to do something about how terrible the situation was) of the new 4.0 bindings. As we are now concentrating all our effort on 4.0 and zero effort on 2.x, because the old bindings only ever half worked, becuase they leak like a sive, and because there are virtually zero applications that actually use them, we are actively trying to get rid of them. So you can stabilize if you want, but mask heading for removal would be better. I'm going to encourage Josh to put a DEPENDS blocks {all the old libs} when you eventually package the new release. [This isn't like Apache 1.3 or GNOME 1.4 where we have to keep it around for ever because legacy apps use it. The old java-gnome never made it past beta. The sooner we expunge it, the better] AfC Maintainer java-gnome: Opening GTK and GNOME to Java programmers!
*** This bug has been marked as a duplicate of bug 160002 ***
