From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [Proposal] Eclass for nodejs modules
Date: Mon, 29 Feb 2016 19:00:56 -0500 [thread overview]
Message-ID: <56D4DBB8.8010201@gentoo.org> (raw)
In-Reply-To: <56D4D33E.6050100@gmail.com>
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.
next prev parent reply other threads:[~2016-03-01 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 9:38 [gentoo-dev] [Proposal] Eclass for nodejs modules Geaaru
2016-02-29 10:12 ` Andrew Udvare
2016-02-29 11:23 ` Geaaru
2016-02-29 23:24 ` Andrew Udvare
2016-03-01 0:00 ` Michael Orlitzky [this message]
2016-03-01 0:28 ` Jesus Rivero (Neurogeek)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56D4DBB8.8010201@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox