Attached is an ebuild for pydev, a Python development plugin for Eclipse -- quite usable.
Created attachment 35850 [details]
I should add that the ebuild cannot use the eclass eclipse-ext, which is
ostensibly broken for eclipse-3 (required by pydev-0.5.0).
Can this be reworked to compile from source code? If not, I don't see much advantage over using the Update Manager built into Eclipse.
Also, you claim eclipse-ext is broken for 3.0. Can you explain that in a
bit more detail?
eclipse-3 does not seem to know to look in /opt/eclipse-extensions-3, so plugins must be installed in /usr/lib/eclipse-3.
Similar issue with the CDT plugin:
* Binary extension
Well, there are other binary-only plugins in Portage, i.e. dev-util/eclipse-*-bin, though I can't give a good argument why this is superior to the Update Manager apart from user convenience.
It is correct that eclipse does not automatically look in /opt/eclipse-extensions-3. This must be added manually at the moment.
Whenever you install an extension, a URL is output,
that will explain how to att /opt/eclipse-extensions-3.
Of course, this should be solved with linked sites, but I've just not gotten
around to it. If you can supply me with a patch against eclipse-sdk-3.0.0-rX,
for this, I'll apply it.
In any event, we cannot install binary-only packages in /usr. It is against
Unfortunately, I can't commit to mucking around in the eclipse source to automate the linking to /opt/eclipse-extensions-3.
I am attaching a pydev ebuild which inherits eclipse-ext, and doing the save for cdt here:
Created attachment 36362 [details]
I'll commit this when I've reworked it to compile pydev from sources.
If you want to speed up the process, you could help out by:
1) pick out the src.zip, unpack at, slap in a build.xml file, say the
one from eclipse-cbg-editor, modify it and build.properties to values
relevant to pydev.
2) make sure that it actually builds, preferrably with both jikes and
3) pack up any patches, and your modified build.xml, build.properties
and attach them to this ebuild.
At that point, I'll make a pydev-<version>-gentoo.tar.bz2 of the source
code, and finish the ebuild.
At any event, this is something I'm going to do. I use pydev myself, and
though it's still a bit shaky, it's the best python editor for eclipse I've
found so far.
the ebuild for
OK -- I don't know how much time I can devote to it. Since it's pure Java, and the only way to get the source is a CVS snapshot, I am personally satisfied with the binary ebuild ...
Err... the newest version pydev-0.8.0 (binary) works fine under Eclipse 3.
Marking it REMIND so that it ends up on the orphaned ebuilds list in the Gentoo Java Wiki.