Uhm, this is the ebuild... Should be selfexplaining :) Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 20579 [details] ebuild for eclipse platform bin 2.1.2 This is the platform ONLY. The JDT is still the same
Created attachment 20580 [details] JDT 2.1.2 ebuild Only for those, who desire the Versionchange.. ;)
I'd really like to know why Eclipse isn't updated in the portage and is still this plain-gramma's-days-version 2.1. Is it low Priority? I mean, 2.1.1 hasn't even been updated and this Version is REALLY old...
A few months ago we finally started to compile all the stuff from scratch. This means that all the -bin packages will be removed from the tree eventually, it's just that we've not had the time to get the "from-source" packages completely stable yet. You can help out by installing the unstable dev-utils/eclipse-sdk-2.1.1 (2.1.2 will be comitted very soon), and help figure out why it always creates new workspaces at bootup. I am not entirely certain it's smart to separate eclipse-sdk into eclipse-platform and eclipse-jdt at this point, as the eclipse project seem to always release the latest version of both in one source bundle. If you have any good reasons for creating a dev-util/eclipse-platfrom (not -bin!), and a separate dev-util/eclipse-jdt, please tell me, and submit an ebuild for the jdt that compiles everythiing from sources using javac. Then, when I find somebody who can write the eclipse-platform ebuild so that it compiles everything from scratch there as well, we can probably keep the two apart, but at this stage, I don't have enough time to do that myself.
I don't think the "sources from scratch"-argument is valid, because there are still many ebuilds that install binaries like nvidia-drivers or acroread. The SDK is superfluous for the most developers, as Eclipse will mostly be used for Java-Development and not for building Eclipse-Plugins, which the sources in the SDK provides. The JDT and the Platform are 11MB and 17MB, while the SDK is ~68MB. 40MB, which most people don't need. I will stay with just JDT and Platform, and create the ebuilds myself, if you don't like to add them to the portage. But make sure, that you are Up2Date with your SDK-Source-Ebuilds, because they are people who'd like to choose, what they want to install and don't want to wait for a 1%-more-performance-ebuild. If you like to play with sources only, please feel free to do that, but be sure to add the binaries, too, while the sources-ebuilds aren't finished, so others can keep on their "productive" working...
Created attachment 20933 [details] SDK 2.1.2 The 2.1.2 SDK-bin.Ebuild for those who want it. I checked out the Source-Variant of the SDK-Ebuild, and it's missing startup.jar...
I can't seem to reproduce your problem with a missing setup.jar for the eclipse-sdk-2.1.2.ebuild. After installation, the startup.jar resides in /usr/lib/eclipse/plugins/org.eclipse.platform/startup.jar However, that doesn't mean you are mistaken, so if this problem persists, please include a complete printout of the package contents: etcat files eclipse-sdk > eclipse-sdk-2.1.2.contents.txt In the meantime, I consider this matter closed, as we have a 2.1.2 ebuild in the tree.
Tested it again today, and the jar-file now seems to be there. Strange though. I tested the workspace-stuff and -data doesn't work with anything but "~/workspace". Whenever I create a different workspace, e.g. using the env-variable from /usr/bin/eclipse it wants to finish installation. Using just ~/workspace as environment works fine for me. Anyway, the binary works with any combination you set, so I will stick to the binary, as long as this Problem isn't fixed with the Source-Variant
