Summary: | Bump to dev-util/eclipse-sdk-3.4.1 request | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Vasilis Lourdas <bugs> |
Component: | New packages | Assignee: | Development Tools Team <dev-tools> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | java, jesse, jrmalaq, magowiz, Manfred.Knick, Michael.Gaber, premek, remy, spatz, xenoterracide |
Priority: | High | ||
Version: | 2008.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
eclipse-sdk-3.4.2.ebuild
sat4j-core-2.0.5.ebuild sat4j-pseudo-2.0.5.ebuild |
Description
Vasilis Lourdas
2008-09-28 15:50:07 UTC
It is in java-overlay. (In reply to comment #1) > It is in java-overlay. Ivan, thank you very much for your appreciated hint. Perhaps you don't mind me adding a warning to users not using paludis or portage-2.2_rc11 ff: I dont mind to have to add a few hand-picked packages to package.keywords - but then I had to discover that in order to emerge eclipse-sdk, one of the needed dependencies is dev-java/ant-apache-bsf-1.7.1, which itself is masked by: EAPI 2, <--------- !!! for which Portage support only will come along with 2.2, for which only Release Candidates exist yet. And thus this little adventure entails a slew of changes to an otherwise rock-solid stable system. A look into BUG #210077: "[TRACKER] sys-apps/portage-2.2" clarified that at least for me, above finding about EAPI-2 breaks the neck for now. BTW: http://overlays.gentoo.org/proj/java/wiki/overlays clearly defines: "Java Overlay Contains java packages that are maintained and in working condition, but not needed in the main tree, <-------------------------------- ??? while still interesting to e.g. java developers (libraries without end-user app depending on them, <--- superseded applications with dead upstream)." <--- I would really appreciate very much not having to pull in all those just in order to have esp. the bug-fixes applied which are contained in SR1. There is an alternative until the Java team could overcome it's caution / reluctance and pull it into Portage at least in a masked manner: Extracting only the absolutely necessary minimum from the overlay into an (otherwise empty) local overlay. But then, I stumbled across the EAPI-2 / Portage 2.2 RC hassle above. The upgrade from 3.4.0-r2 to 3.4.1 worked great for me on ~amd64. It's also great that p2 works now. Thanks a lot for the excellent work! Looking forward to you getting it in the tree :) Now it is eclipse-sdk-3.4.2. Created attachment 185397 [details]
eclipse-sdk-3.4.2.ebuild
Created attachment 185398 [details]
sat4j-core-2.0.5.ebuild
Created attachment 185399 [details]
sat4j-pseudo-2.0.5.ebuild
The above ebuilds have been only slightly modified to respect new version numbers for downloading. Otherwise they are from the java overlay. You will need a symbolic link: # ll .../local-overlay/dev-util/eclipse-sdk ... eclipserc-3.4 -> eclipserc ... Any hope of getting 3.4.2 out of the overlay ghetto, at least in unstable-x86? Thanks. We don't need two bugs for a version bump request. *** This bug has been marked as a duplicate of bug 229609 *** |