From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 0/2] nodejs cleanup and add
Date: Tue, 1 Dec 2015 12:15:49 -0500 [thread overview]
Message-ID: <1448990151-27720-1-git-send-email-twoerner@gmail.com> (raw)
The current stable version of nodejs is 4.2.2.
Currently there are two nodejs recipes from which to choose: nodejs, and
nodejs4. A user would naturally assume nodejs4 refers to version 4.2.2, but
they would be wrong. Nodejs4 refers to version 0.4.12.
Cleanup the current nodejs naming and include a new recipe for the latest
stable version.
Trevor Woerner (2):
nodejs: cleanup
nodejs: add recipe for latest stable
.../enable-armv5e-build.patch | 0
.../{nodejs => nodejs-0.12.7}/no-registry.patch | 0
.../libev-cross-cc_0.4.12.patch | 0
meta-oe/recipes-devtools/nodejs/nodejs.inc | 80 ++++++++++++++++++++++
meta-oe/recipes-devtools/nodejs/nodejs_0.12.7.bb | 74 +-------------------
.../nodejs/{nodejs4_0.4.12.bb => nodejs_0.4.12.bb} | 2 +-
meta-oe/recipes-devtools/nodejs/nodejs_4.2.2.bb | 9 +++
7 files changed, 92 insertions(+), 73 deletions(-)
rename meta-oe/recipes-devtools/nodejs/{nodejs => nodejs-0.12.7}/enable-armv5e-build.patch (100%)
rename meta-oe/recipes-devtools/nodejs/{nodejs => nodejs-0.12.7}/no-registry.patch (100%)
rename meta-oe/recipes-devtools/nodejs/{nodejs4 => nodejs-0.4.12}/libev-cross-cc_0.4.12.patch (100%)
create mode 100644 meta-oe/recipes-devtools/nodejs/nodejs.inc
rename meta-oe/recipes-devtools/nodejs/{nodejs4_0.4.12.bb => nodejs_0.4.12.bb} (87%)
create mode 100644 meta-oe/recipes-devtools/nodejs/nodejs_4.2.2.bb
--
2.6.0.rc3
next reply other threads:[~2015-12-01 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 17:15 Trevor Woerner [this message]
2015-12-01 17:15 ` [meta-oe][PATCH 1/2] nodejs: cleanup Trevor Woerner
2015-12-01 17:22 ` Martin Jansa
2015-12-01 17:43 ` Trevor Woerner
2015-12-01 17:15 ` [meta-oe][PATCH 2/2] nodejs: add recipe for latest stable Trevor Woerner
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=1448990151-27720-1-git-send-email-twoerner@gmail.com \
--to=twoerner@gmail.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.