I'm having trouble getting this to build properly. Attaching my attempt...
Created attachment 120625 [details] pauker-1.7.5.ebuild
(In reply to comment #0) > I'm having trouble getting this to build properly. > > Attaching my attempt... > So do you need input from us or is this just a reminder bug?
I'd appreciate some help
(In reply to comment #3) > I'd appreciate some help > Then the actual failure would be useful instead of requiring as to download & compile ourselves just to point out something that we could point out from the logs.
(In reply to comment #4) > (In reply to comment #3) > > I'd appreciate some help > > > > Then the actual failure would be useful instead of requiring as to download & > compile ourselves just to point out something that we could point out from the > logs. > oh yeah, sorry... $ pauker Exception in thread "main" java.lang.NoClassDefFoundError: edu/stanford/ejalbert/exception/UnsupportedOperatingSystemException
(In reply to comment #5) > $ pauker > Exception in thread "main" java.lang.NoClassDefFoundError: > edu/stanford/ejalbert/exception/UnsupportedOperatingSystemException If you have dependencies, using --jar with dolauncher (as you do implicitly) won't make them load (unless you hardcode their paths to manifest's CLASSPATH which we don't do because it's ugly :). Upstream jar just bundles them inside, nasty and usual... Pass `--main $main_class` to dolauncher (the class name you pass to `jar -e` which you don't need to anymore). Also, using jar -C classes is bit more elegant than cd classes; jar ... :) # jar cf ${PN}.jar -C classes . || die "jar failed"
You'll also have to either point the --pre in dolauncher to GAMES_DATADIR or install the resources in GAMES_DATADIR/pauker/pauker because it expects them to be in ./pauker relative to the PWD... (as upstream has them in ./pauker dir relative to jar's "root"). Also, you can change the jdk/jre dep to >=1.4, it works fine.
works now, thanks :)
