Greetings again, Attached is an ebuild for the ncc a (the) compiler for the Nemerle language. Nemerle is a hybrid functional-imperative-object oriented language for the .NET platform. It is compatible with the mono project's .NET implementation for linux. I'm thinking this could be dev-lang/nemerle. It depends on xspp, which I also submitted an ebuild for (bug #42209 [I assumed in this ebuild that xspp would be in app-text/xspp]). Thanks, Robert
Created attachment 25959 [details] The nemerle license
Created attachment 25960 [details] The ebuild file
Created attachment 30375 [details] nemerle-0.1.2 ebuild
Created attachment 30376 [details, diff] patch to fix Makefile error Patch to fix build error in ncc/Makefile for 0.1.2 release. Patch has been submitted to upstream maintainers via nemerle.org/bugs.
Why have you set dependencies for libxslt, python and xspp? Shouldn't it be just mono? I don't see that Nemerle needs it and e.g. I haven't installed xspp. Tim
low prio, early in development
Created attachment 33552 [details] nemerle-0.1.3.ebuild I don't use "make install" for installation, because I got an error and a short look at the makefiles did not solve it. So I installed manually by doXXX. Tim
Created attachment 34466 [details] Cleaned up ebuild Okay, here's a cleaned up ebuild for 0.1.4. I'm hesitant to add nemerle to portage just yet, but here's the ebuild if people want to test.
It works fine for me. But I don't understand why it is such a "problem" to add nemerle to portage? Tim
Okay, i've just added this in, minus the xspp dep. If the text people get around to adding xspp, i will put that dep in behind the "doc" USE flag. I don't want to add xspp myself as 1) it isn't a hard dep, 2) it's not my herd and it would run the risk of being added but not maintained. Marking LATER (/TESTREQUEST), please report back success/failure with the ebuild, and feel free to reopen based on the status of #42209.
