Created attachment 371148 [details] dev-lisp/picolisp-3.1.5.ebuild New ebuild for great developement system PicoLisp. http://picolisp.com Description from site: PicoLisp: The Scalpel of Programming A Radical Approach to Software Development If some programming languages claim to be the "Swiss Army Knife of Programming", then PicoLisp may well be called the "Scalpel of Programming": Sharp, accurate, small and lightweight, but also dangerous in the hand of the inexperienced. Less is more! - The maxim is: Keep it simple, and the programmer in control!
Created attachment 371270 [details] dev-lisp/picolisp-3.1.5.ebuild
Created attachment 371272 [details] dev-lisp/picolisp-9999.ebuild Same contents as previous
I'm working on the ebuild and will push it on the tree after some testing, do you mind if I drop multilib support for the moment cause the ebuild fails at all on my no-multilib profiled box? Also, is there a specific reason for the sstrip stuff you're doing in src_install? Btw, Please reply to me here or by email with your full name in Latin characters so that I can credit you properly. Thank you for the ebuild and the bug.
Now in lisp overlay. http://git.overlays.gentoo.org/gitweb/?p=proj/lisp.git;a=commit;h=a352f2b53c26c8c60b3e2094ded4e16bdb9ef1fc
Sorry for long answer, now I turned on email notifications. > do you mind if I drop multilib support for the moment cause the ebuild fails > at all on my no-multilib profiled box? Do you mean to drop no-multilib support? It's ok for now. But I wish to add support for no-multilib. There is a problem: to build 64-bit version of PicoLisp other instance of PicoLisp needed. Either 32-bit version of PicoLisp that written in C and can be built by GCC, or Ersatz (Java version of Picolisp) that requires JDK, or prebuilt PicoLisp. Some solutions: * Add "java" use-flag to build by Ersatz. * Make a prebuilt PicoLisp64, add it to distfiles and use it to build local PicoLisp. What solution do you think is the best? > Also, is there a specific reason for > the sstrip stuff you're doing in src_install? No. I used it in my overlay and I like minimum size. > Btw, Please reply to me here or by email with your full name in Latin > characters so that I can credit you properly. Here is my full name transliterated from Ukrainian: Kostyatyn Bytenskyi. In English manner: Constantine Bytenski.
Created attachment 386818 [details] dev-lisp/picolisp-9999.ebuild
Created attachment 386820 [details] dev-lisp/picolisp-3.1.5.ebuild
Created attachment 386822 [details] dev-lisp/picolisp-3.1.8.ebuild
Created attachment 386824 [details] picolisp-3.1.8.ebuild
Created attachment 386826 [details] picolisp-9999.ebuild
I added support for non-multilib. Also I removed sstrip and did some minor changes.
Is anybody here?
I'm here but working on other stuff atm. I'll try work on this later this month, if not please remind me. Thank you for your work.
Don't add arch testing teams to non-arch testing bugs. Removing x86 and amd64.
Created attachment 448710 [details] picolisp-9999.ebuild
Created attachment 448712 [details] picolisp-16.6.ebuild Is anybody here?
Thanks for your work and sorry for this long delay. I've pushed this ebuild to the overlay with some changes to improve its quality: https://gitweb.gentoo.org/proj/lisp.git/commit/?id=de410db0d5c7eea1f48d21b7a1664fc39bbf3aaa Please, check that everything is ok and reopen this bug if necessary.
Created attachment 690762 [details] picolisp-9999.ebuild
I made updated ebuild for pil21, which uses Clang. I dont’t know what to do to share new version of ebuild, so I changed status of this bug.
Created attachment 728949 [details] picolisp-9999.ebuild
