From: "Herb Miller Jr." <gentooherb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] Begin a dev-libs/nodejs category?
Date: Tue, 20 Mar 2018 07:50:53 -0400 [thread overview]
Message-ID: <6d081572-1b9a-663e-5993-8143518cf0cd@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
When I did my homework on creating nodejs ebuilds (not nodejs itself but
packages written in node), it seems the topic has come up a few times in
the past but the time commitment and general disorganization of upstream
has scared off any serious attempts at packaging.
Seeing as there has been interest in nodejs packages, and in the end we
could be talking 400-600+ packages, would it be possible to create
dev-libs/nodejs category? I would be happy to write and proxy-maintain
ebuilds for a large number of them to get things in motion. I've already
opened pull request #7427 [1] for chalk and its dependencies. I'm aiming
to build up to all the dependencies needed for Visual Studio Code OSS.
[1]:https://github.com/gentoo/gentoo/pull/7427
----
Herb Miller Jr.
[-- Attachment #2: Type: text/html, Size: 22128 bytes --]
next reply other threads:[~2018-03-20 11:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 11:50 Herb Miller Jr. [this message]
2018-03-20 18:34 ` [gentoo-dev] [RFC] Begin a dev-libs/nodejs category? Michał Górny
2018-03-20 19:43 ` Herb Miller Jr.
2018-03-20 18:48 ` Michael Orlitzky
2018-03-20 20:14 ` Herb Miller Jr.
2018-03-20 20:44 ` Michael Orlitzky
2018-03-21 1:27 ` Kent Fredric
2018-03-21 1:36 ` M. J. Everitt
2018-03-20 23:50 ` Benda Xu
2018-03-21 1:44 ` Herb Miller Jr.
2018-03-21 7:33 ` Kent Fredric
2018-03-21 12:22 ` Herb Miller Jr.
2018-03-21 10:07 ` X dej
2018-03-21 12:15 ` [gentoo-dev] Pypi generator (Was: [RFC] Begin a dev-libs/nodejs category?) Benda Xu
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=6d081572-1b9a-663e-5993-8143518cf0cd@gmail.com \
--to=gentooherb@gmail.com \
--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