Hi, I did an ebuild that will build SableVM out of the SableVM subversion repository (see attached file). SableVM is an open-source Java Virtual Machine that uses the GNU Classpath library. In portage there are already ebuild for SableVM point releases. However, sometimes the releases are far apart (most developers attending university, exams, papers or other deadlines). Some times significant amount of changes and bug fixes have been done in the subversion repository. Daily source based snapshot are available from the SableVM website, however, they require extra work from the user. SableVM developers would like to automate the build of daily binary packages for various OSes/distributions. This ebuild gets the staging branch sources and builds them. The staging branch is kept quite stable at all time since each developer tests its individual work in a seperate developer sandbox. Only well-tested code gets into the staging branch. David B
Hi, I did an ebuild that will build SableVM out of the SableVM subversion repository (see attached file). SableVM is an open-source Java Virtual Machine that uses the GNU Classpath library. In portage there are already ebuild for SableVM point releases. However, sometimes the releases are far apart (most developers attending university, exams, papers or other deadlines). Some times significant amount of changes and bug fixes have been done in the subversion repository. Daily source based snapshot are available from the SableVM website, however, they require extra work from the user. SableVM developers would like to automate the build of daily binary packages for various OSes/distributions. This ebuild gets the staging branch sources and builds them. The staging branch is kept quite stable at all time since each developer tests its individual work in a seperate developer sandbox. Only well-tested code gets into the staging branch. David Bélanger, SableVM developer
Created attachment 45038 [details] sablevm-svn ebuild
Hi, Should you decide to include it in portage, please add: !dev-java/sablevm-svn to the currently existing dev-java/sablevm ebuilds as both packages cannot co-exist. Thanks, David
I'm not sure we have the capacity to handle bugs for this ebuild officially. However, we are creating an "unofficial" tree for experimental java ebuilds that this one would fit in nicely, if you are interested. Users will be able to subscribe to the unofficial tree as an overlay, but we don't guarantee *any* support for it. Reopen the bug with a "yes", if you're interested in this.
Yes, I will be interested to have it in the experimental tree. Users can report bugs directly to http://sablevm.org/bugs.html and specify "staging" for the version. I am testing newer ebuild version that will add a postinst message for this. I will attach it shortly.
Created attachment 46222 [details] Updated ebuild
IMO, we should use the upstream snapshots (done daily) instead of SVN. And maybe bump those snapshots about once a week... unless we've got permission from their developers it's ok for us to (ab)use their repo in that way.
D'oh, I didn't read this thoroughly the first time. But I suppose it warrants some clarification -- you guys prefer us to use the repo instead of snapshots?
Hi, Just to make it clear, the SableVM team does not see any problem using it directly from the SVN repository. They are actually more worried about Gentoo users setting their own less-safe CFLAGS then reporting bug reports about problems :) Although getting it from SVN the first time uses more CPU and I/O ressources than the snapshot, subsequent updates usually take much less bandwidth as only the difference is transfered instead of the full source (provided that the distfiles are not erased). I could also eventually "improve" the ebuild to take the snapshot (which is basically a SVN snapshot) if svn files are not present in distfiles and do a svn update after. David
# William L Thomson Jr <wltjr@gentoo.org> (13 Jun 2007) # Stale upstream older versions than last release in tree. # Package will be moved to junkyard overlay after 30 days # unless users express interest in this package. dev-java/sablevm Either way we are not going to include live CVS ebuilds in the main tree. If development of Sable VM pick up again, we are happy to consider it for java-experimental overlay. In that case contact us on #gentoo-java in FreeNode for example.
