http://www.cs.uu.nl/helium/download.html When version bumping you should start using the generation 2 eclasses (java-pkg-2, java-ant-2). Please run the new ebuild through the java team to ensure that it follows our standards.
*helium-1.6 (06 Apr 2007) 06 Apr 2007; Andres Loeh <kosmikus@gentoo.org> +files/helium-wrapper-1.6, +helium-1.6.ebuild: Added new version 1.6, which is going to replace the broken older ebuilds. Seems kosmikus didn't notice this bug so let's just make this a gen 2 migration. kosmikus: if you don't respond to this bug in a couple of weeks we will do the migration ourselves.
Seems the 1.6 ebuild he committed doesn't use java eclasses so we just have to get rid of the old ebuilds so making this a stable request.
kosmikus is retiring
Haskell: please consider if 1.6 can be stabilized and CC x86 if yes. The old versions are one of the last few packages that still use gen1 java eclass.
It turns out that helium-1.6 doesn't build with the latest stable dev-lang/ghc (6.8.x). We'll look into patching the build system, wait 30 days and then stabilize. Ok?
(In reply to comment #5) > > We'll look into patching the build system, wait 30 days and then stabilize. > Ok? > sure
(In reply to comment #5) > It turns out that helium-1.6 doesn't build with the latest stable dev-lang/ghc > (6.8.x). > > We'll look into patching the build system, wait 30 days and then stabilize. > Ok? > How's this coming along?
Any news? helium is one of last 3 packages using the old gen1 java eclasses. Also I wonder if you need the eclass at all? In 1.6 you removed it from inherit. In both 1.1 and 1.6 the only thing that could need java (after first look) is interpreter/Hi.java for which I couldn't find any reference in makefiles or anywhere. Does it mean it really doesn't need java? In that case we could just remove java-pkg from inherit in 1.1 and 1.2 and be done.
I don't have an x86 machine atm to test, is the changes easily done? There is also a console interpreter, so I think we could do without the GUI in java, it seems quite minimalistic anyway and just wraps the console app. It's just a single java file though, should be simple to install using the new java eclasses too? However, I could not get it to work properly, so I'd vote to just not install it :)
(In reply to comment #9) > I don't have an x86 machine atm to test, is the changes easily done? I don't have gcc 3.x required for the ghc used in helium 1.1/1.2 to test, but the changes should be easy yes. > There is also a console interpreter, so I think we could do without the GUI in > java, it seems quite minimalistic anyway and just wraps the console app. > It's just a single java file though, should be simple to install using the new > java eclasses too? Oh I see, you are just directly downloading and installing the .jar, well that's done the same way in new eclasses. So a simple change in inherit from java-pkg to java-pkg-2 should work. > However, I could not get it to work properly, so I'd vote to just not install > it :) That's another option, in that case java-pkg can be removed from inherit altogether, as done in 1.6.
I'd like to do this to both ebuilds: diff -u -B -r1.20 helium-1.1.ebuild --- helium-1.1.ebuild 31 Oct 2007 13:22:01 -0000 1.20 +++ helium-1.1.ebuild 10 Feb 2009 19:17:58 -0000 @@ -2,7 +2,7 @@ # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/dev-lang/helium/helium-1.1.ebuild,v 1.20 2007/10/31 13:22:01 dcoutts Exp $ -inherit java-pkg +inherit java-utils-2 DESCRIPTION="Helium (for learning Haskell)" HOMEPAGE="http://www.cs.uu.nl/helium" Meaning just to convert into the new eclasses. It requires an ancient version of the ghc compiler, I doubt anyone actually uses 1.1 or 1.2 of helium.
(In reply to comment #11) > -inherit java-pkg > +inherit java-utils-2 You can't inherit java-utils-2 directly. You need to inherit java-pkg-2 instead.
(In reply to comment #12) > (In reply to comment #11) > > -inherit java-pkg > > +inherit java-utils-2 > > You can't inherit java-utils-2 directly. You need to inherit java-pkg-2 > instead. > Ok, so -inherit java-pkg +inherit java-pkg-2 then. Dare I change this without a machine to test it on? Any takers? :)
Created attachment 181586 [details, diff] patch to migrate to gen2 OK tried to test the migration by commenting the build, leaving just the java stuff, and there was really a catch :) the gen2 java-pkg_dojar() treats symlinks differently and DISTDIR contains symlinks. The patch is therefore copying the jar to WORKDIR first. I've also changed the unnecessary jdk dep to a versioned jre dep.
(In reply to comment #14) > Created an attachment (id=181586) [edit] > patch to migrate to gen2 Just applied it, no more gen-1. Leaving the original stable request to your consideration.
Are we able to move this defect alone? Thanks
(In reply to comment #16) > Are we able to move this defect alone? > > Thanks > along. sorry 4:30 am brains work slowly.
(In reply to comment #16) > Are we able to move this defect alone? > > Thanks > Yes. Let's add arches as haskell seems inactive.
Helium 1.6 is 4 years old, dead upstream and not a lot of action around it at all in the community. I'm not sure it even compiles with recent GHC versions? I don't have the hardware to test.
I wouldn't quite say "dead upstream": upstream _is_ using it and is developing more infrastructure around it (such as a plagiarism detector), but they're no longer updating it (and it seems that upstream are the only users of Helium). (This is what I came out with from a talk with one of Helium's developers earlier this year.)
Please fix bug 212725 before stabilization.
After installing the missing deps I was running into the --as-needed failures of bug 247044 :(
This package is definitely not ready, see Thomas' comments above. Please re-open when these issues are fixed.
I've talked to upstream about getting a fixed version. Awaiting reply. In the current state I can't say I'd like helium to be stable, or even present in portage at all. Let's see what upstream thinks.
