Since OSUNIX is using ebuilds with pkgcore to build all packages it works really well with python/c/c++ code, but for java it's just plain ugly. What to do? I'm faced with the choice to either mangle and fight with what gentoo java devs are doing or to find some other sensible path. So why not use jpackage?
1) It won't have any gentoo'isms
2) Distro agnostic
3) They are working on things like jdk6
4) maven2 already builds
So why not help a group that's on the right path?
They're using Koji which *really* sucks.. So if you can't get their cvs to work..
setenv CVSROOT :pserver:anonymous@jpackage.org:/home/projects/jpackage/cvs
cvs login (hit enter)
mkdir jpackage ; cd jpackage
cvs -z3 checkout .
From there you'll have a cvs checkout of their current repo. All the stuff I'm interested in is in the **/devel directory. So hopefully I can script convert this from spec files to ebuilds. Then we'll have everything jpackage has! (and a way to convert pkg5 spec files over to ebuild as well)