Please find the attached ebuild newlisp-8.9.0.ebuild. newLISP is, as the name suggests, a new scripting language dialect of LISP for general programming, web applications, AI, and statistics. It seems to be a powerful and expressive language and could be a useful addition to the Portage tree. I suggest this be filed as dev-lisp/newlisp.
Created attachment 94000 [details] ebuild for newlisp
Hi Rafael, it might take a while to get a maintainer for this, but would you consider sending a patch from the darcs gentoo lisp repository? See: http://www.gentoo.org/proj/en/common-lisp/index.xml If you need a hand with darcs, just ask. Although I have a short darcs guide in the works.
current stable version is 9.1, released February 15th, 2007
Submitted ebuild for 9.1.1. Tested on x86 with following flags: USE="-* readline tcltk unicode" emerge newlisp USE="-* readline tcltk" emerge newlisp USE="-* readline unicode" emerge newlisp USE="-* readline" emerge newlisp USE="-* tcltk unicode" emerge newlisp USE="-* tcltk" emerge newlisp USE="-* unicode" emerge newlisp USE="-*" emerge newlisp
(In reply to comment #4) > Submitted ebuild for 9.1.1. (In our development overlay, for the moment. More info #gentoo-lisp)
please test 9.2.0 ebuild at <http://repo.or.cz/w/gentoo-lisp-overlay.git?a=blob;f=dev-lisp/newlisp/newlisp-9.2.0.ebuild;h=906a68ea6392c73a00fc66d1ce4736677ce4f924;hb=bd35facc0afedcae7bed7146c535847ac74276bc>
(In reply to comment #6) > please test 9.2.0 ebuild at > <http://repo.or.cz/w/gentoo-lisp-overlay.git?a=blob;f=dev-lisp/newlisp/newlisp-9.2.0.ebuild;h=906a68ea6392c73a00fc66d1ce4736677ce4f924;hb=bd35facc0afedcae7bed7146c535847ac74276bc> > <http://repo.or.cz/w/gentoo-lisp-overlay.git?a=blob_plain;f=dev-lisp/newlisp/newlisp-9.2.0.ebuild;hb=bd35facc0afedcae7bed7146c535847ac74276bc> for the actual ebuild without fluff
I've added 10.1.1 to the lisp overlay. If you want this in main tree, then work with upstream so that I can remove the non-gentoo-specific sed magic.
Version 10.5.4 pushed to the lisp overlay *** This bug has been marked as a duplicate of bug 359245 ***