From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/nodejs: Add node.js v4.1.2
Date: Thu, 08 Oct 2015 00:04:15 +0200 [thread overview]
Message-ID: <1444255455.5183.2.camel@embedded.rocks> (raw)
In-Reply-To: <87612jnl7c.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Mi, 2015-10-07 at 10:20 +0200, Peter Korsgaard wrote:
> > > > > > "Jaap" == Jaap Crezee <jaap@jcz.nl> writes:
>
> > Signed-off-by: Jaap Crezee <jaap@jcz.nl>
> > ---
> > ...01-Remove-dependency-on-Python-bz2-module.patch | 31
> ++++++++++++++++++++++
> > package/nodejs/Config.in | 5 ++++
> > package/nodejs/nodejs.hash | 3 +++
> > 3 files changed, 39 insertions(+)
> > create mode 100644 package/nodejs/4.1.2/0001-Remove-dependency-on
> -Python-bz2-module.patch
>
> > +++ b/package/nodejs/Config.in
> > @@ -40,12 +40,17 @@ config BR2_BR2_PACKAGE_NODEJS_0_12_X
> > bool "v0.12.7"
> > depends on !BR2_ARM_CPU_ARMV5
>
> > +config BR2_BR2_PACKAGE_NODEJS_4_1_X
> > + bool "v4.1.2"
> > + depends on !BR2_ARM_CPU_ARMV5
> > +
> > endchoice
>
> > config BR2_PACKAGE_NODEJS_VERSION_STRING
> > string
> > default "0.10.40" if BR2_BR2_PACKAGE_NODEJS_0_10_X
> > default "0.12.7" if BR2_BR2_PACKAGE_NODEJS_0_12_X
> > + default "4.1.2" if BR2_BR2_PACKAGE_NODEJS_4_1_X
>
> Is there a need to keep both 0.12.x and 4.1.x? The only reason we
> have a
> version selection is afaik that <ARMv7 is only supported in the old
> 0.10.x version.
>
Yes, there is! Node.js applications written for Node.js 0.12.x are not
necessarily compatible with Node.js 4.x.
Best regards
J?rg Krause
next prev parent reply other threads:[~2015-10-07 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 12:57 [Buildroot] [PATCH 1/1] package/nodejs: Add node.js v4.1.2 Jaap Crezee
2015-10-07 8:20 ` Peter Korsgaard
2015-10-07 12:26 ` Jaap Crezee
2015-10-07 22:04 ` Jörg Krause [this message]
2015-10-09 7:03 ` Peter Korsgaard
2015-10-09 7:13 ` Jörg Krause
2015-10-07 22:44 ` Jörg Krause
2015-10-08 9:26 ` Jaap Crezee
2015-10-19 16:34 ` Yann E. MORIN
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=1444255455.5183.2.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=buildroot@busybox.net \
/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