Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/nodejs: Add version 5.2.0
Date: Mon, 14 Dec 2015 21:43:37 +0100	[thread overview]
Message-ID: <20151214214337.2933ea41@free-electrons.com> (raw)
In-Reply-To: <CAFGQKxfvQwA3v8W=OKEvNR6SE06DTng6PxQGj4q7o4zUWYbU2g@mail.gmail.com>

Hello,

On Mon, 14 Dec 2015 20:24:30 +0000, Martin Bark wrote:

> I'm not sure the answer to that.  What i can say is that all four are
> getting maintained.  Also, according to https://github.com/nodejs/LTS
> node.js 0.10.x will be maintained all the way until October 2016.
> 
> I see two logical approaches for buildroot:
> 
> 1) Support all four in buildroot because node.js support all four
> 2) Only Support the 4.x and 5.x because they are the current LTS and
> Stable releases (i.e. the ones on the front page of
> https://nodejs.org)
> 
> Personally I'd vote for 2) because it simplifies things.
> 
> What are your thoughts?

I'm fine with option (2) as well, but do we have other NodeJS users
that would like to see 0.10.x and 0.12.x being kept?

Is there any issue for users of 0.10.x/0.12.x to migrate to 4.2 or 5.2 ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-12-14 20:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 19:44 [Buildroot] [PATCH 1/3] package/nodejs: Add version 5.2.0 Martin Bark
2015-12-14 19:44 ` [Buildroot] [PATCH 2/3] package/nodejs: Fix uClibc-ng support Martin Bark
2015-12-14 19:44 ` [Buildroot] [PATCH 3/3] package/libuv: Fix support for uClibc-ng Martin Bark
2015-12-14 20:09 ` [Buildroot] [PATCH 1/3] package/nodejs: Add version 5.2.0 Thomas Petazzoni
2015-12-14 20:24   ` Martin Bark
2015-12-14 20:43     ` Thomas Petazzoni [this message]
2015-12-14 21:10       ` Yann E. MORIN
2015-12-14 21:31         ` Martin Bark
2015-12-14 21:49           ` Yann E. MORIN
2015-12-14 22:35         ` Jörg Krause
2015-12-16 11:26           ` Vicente Olivert Riera
2015-12-16 13:41             ` Thomas Petazzoni
2015-12-16 16:39               ` Yann E. MORIN
2015-12-17 17:29                 ` Martin Bark
2015-12-17 18:27                   ` Yann E. MORIN
2015-12-17 19:55                     ` Martin Bark
2015-12-17 20:05                       ` 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=20151214214337.2933ea41@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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