# My first ebuild submission :) Hope I did it right. DESCRIPTION="Eclipse Tools Platform" HOMEPAGE="http://www.eclipse.org/" SRC_URI="http://download.eclipse.org/downloads/drops/R-2.1-200303272130/eclipse-SDK-2.1-linux-gtk.zip" IUSE="" SLOT="0" LICENSE="CPL-1.0" KEYWORDS="~x86 ~ppc ~sparc" DEPEND=">=virtual/jdk-1.3 =x11-libs/gtk+-2* ppc? ( app-shells/tcsh )" RDEPEND=">=virtual/jdk-1.3 =x11-libs/gtk+-2*" S=${WORKDIR}/eclipse src_install() { dodir /opt/eclipse cp -dpR features install.ini eclipse \ icon.xpm plugins startup.jar \ ${D}/opt/eclipse/ dohtml cpl-v10.html notice.html readme/* dodir /etc/env.d echo -e "LDPATH=/opt/eclipse\nPATH=/opt/eclipse\nROOTPATH=/opt/eclipse" > ${D}/etc/env.d/20eclipse } Reproducible: Always Steps to Reproduce:
eclipse binary stuff is already in portage, they just need bumpage to 2.1
Is there any particular reason for Eclipse 2.1 not to be marked stable? I run it almost daily on x86 and it works like a charm (once GTK+ 2.2.1-r1 is installed, see #19084).
There is Bug #39176 on www.eclipse.org ... essentially it says you can't open Window -> Preferences -> Workbench -> Keys if you are using gtk 2.2.2. with gtk 2.2.1 everything is fine...
Ok, interesting. I, however, had severe problems with lockups and similar with Eclipse 2.0 on GTK+. And that version is what is currently marked as "stable"... Better 2.1 than 2.0 is my personal opinion (but I have of course unmasked 2.1 in my PORTAGE_OVERLAY so I don't care much anymore). The bug in GTK+-2.2.1 (fixed in unstable GTK+-2.2.1-r1) causing CPU pegs is of course very irritating as long as that version of GTK+ remains the "stable" one.
This has been superceded by the release of dev-util/eclipse-sdk-2.1.1. Report any and all problems against that one instead.