Keep eye out for release.
2.1.0 (beta) was released: http://www.jazzscheme.org/releases.htm
Live ebuild in lisp overlay.
I adapted the ebuild for 2.1.0 but it did not work, got this error: *** ERROR IN "configure"@5.1 -- Datum expected The following patch works for me (still compiling though) --- /home/pclouds/t/layman/lisp/dev-scheme/jazzscheme/jazzscheme-999.ebuild 2009-02-15 23:15:37.000000000 +1100 +++ /home/pclouds/git/pclouds-overlay/dev-scheme/jazzscheme/jazzscheme-2.1.0.ebuild 2009-02-25 10:23:24.000000000 +1100 @@ -2,13 +2,9 @@ # Distributed under the terms of the GNU General Public License v2 # $Header: $ -inherit git - DESCRIPTION="JazzScheme is an open source programming language based on Scheme." HOMEPAGE="http://www.jazzscheme.org/" -#SRC_URI="http://www-etud.iro.umontreal.ca/~lasallej/${P}.tar.gz" -EGIT_REPO_URI="git://github.com/jazzscheme/jazz_dev.git" -#EGIT_REPO_URI="git://64.235.209.250/git/jazz_dev" +SRC_URI="http://www-etud.iro.umontreal.ca/~lasallej/${P}-devel.tar.gz" LICENSE="|| ( MPL-1.1 GPL-2 )" SLOT="0" @@ -18,13 +14,19 @@ DEPEND="dev-scheme/gambit x11-libs/cairo" RDEPEND="${DEPEND}" +S="${WORKDIR}/${P}-devel" + +jazz_make() { + gsc-gambit -e "(jazz.process-command \"$*\" (console-port))" || die +} + src_compile() { sed "s:gsc-script:gsc-gambit:" -i kernel/build.scm vecho ">>> Configuring..." - gsc-gambit configure || die + jazz_make configure vecho ">>> Building..." - gsc-gambit make jedi || die - gsc-gambit make all || die + jazz_make "make jedi" || die + jazz_make "make all" || die } src_install() {
BTW, forgot to say the ebuild has not dealt with ~/.jazz writing (maybe you have known it already, but anyway)
It looks like you have found a creative way around the limited support for scripted builds that is in 2.1.0. Fortunately that support has been added since. There are lots of other rough edges, some of which have been fixed, so I think the live ebuild is currently the only interesting one to have.
Indeed ~/.jazz writing is one of those other issues that has already been solved by upstream for us.
It seems that there was a release (2.3) some time ago. However it seems that there is no separate tarball. Someone should reestablish contact with upstream and work on this and other remaining issues.
