All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 09 Oct 2015 09:13:13 +0200	[thread overview]
Message-ID: <1444374793.2909.7.camel@embedded.rocks> (raw)
In-Reply-To: <87k2qwbk24.fsf@dell.be.48ers.dk>

Dear Peter,

On Fr, 2015-10-09 at 09:03 +0200, Peter Korsgaard wrote:
> > > > > > "J?rg" == J?rg Krause <joerg.krause@embedded.rocks> writes:
> 
> Hi,
> 
> > > >  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.
> 
> Ok, but where does that leave us? Is the 0.12.x series still
> supported
> upstream? When can it be dropped?
> 

The Node.js foundation has a plan to establish Long-Term Support for
the current releases [1]. However, it is not officially yet.

[1] http://dailyjs.com/2015/07/01/node-long-term-support-working-group/

  reply	other threads:[~2015-10-09  7:13 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
2015-10-09  7:03     ` Peter Korsgaard
2015-10-09  7:13       ` Jörg Krause [this message]
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=1444374793.2909.7.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 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.