On 02/29/2016 06:24 PM, Andrew Udvare wrote: > On 29/02/16 03:23, Geaaru wrote: >> >> In conclusion, it seems that is not accepted use of nodejs modules >> ebuild inside portage. It is right? >> >> > There used to be a CoffeeScript ebuild if you search back. I do not > remember how it worked but IIRC I think it was basically just creating a > fake root for itself. The distfile itself was just that node_modules/ > directory in a tarball. No direction on how those dependencies could be > shared, so it is no longer in the tree. >
I really needed it for one program, so I'm maintaining coffee-script in the tree now as dev-lang/coffee-script. I have an eclass and some ebuilds using it at https://github.com/orlitzky/npm but I didn't want to wind up in charge of a NodeJS project and nobody else did either, so I'm no longer working on it. The current coffee-script ebuild copy/pastes some of the stuff that would have been handled by the eclass. Only misery lies down this path. Every upstream project is a mess and nobody cares, because implicitly, their roadmaps all involve realizing that javascript is awful and abandoning the project. To get this stuff in the tree, we would need a full-time devoted developer who just loves javascript and is sexually aroused by having his time wasted.
