From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot nodejs 6.6.0
Date: Tue, 27 Sep 2016 15:10:38 +0200 [thread overview]
Message-ID: <20160927151038.474df7de@free-electrons.com> (raw)
In-Reply-To: <CAFGQKxcFTgyOWB+h84PgRCVpcpTRYe1q9XrJe3B+dVZAycu1oQ@mail.gmail.com>
Hello,
On Tue, 27 Sep 2016 09:22:02 +0100, Martin Bark wrote:
> > Thanks. From that list I also see that security support for the 0.10.x
> > series will end in October, so we should presumably remove 0.10.x
> > support before the 2016.11 release.
>
> The 0.10.x branch is only included for the armv5 since version > 0.10.x
> dropped support. In the past there was discussion around leavening 0.10.x
> in buildroot even when support ended for it. Personally i would like to
> drop 0.10.x to help tidy up the nodejs package but I'm fine with leaving it
> if people use it.
It is fine to support 0.10.x in Buildroot to support ARMv5 while 0.10.x
is still maintained upstream. But as Peter mentioned, the support for
0.10.x upstream will stop soon, so we should also remove it from
Buildroot.
Yes, it will leave people using ARMv5 without a NodeJS implementation,
but that's upstream decision. If those people are unhappy with upstream
decision, they should talk with upstream directly.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-09-27 13:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6C0FD5AC-BA66-48C8-BC00-3F8393524B7B@bluecordial.com>
2016-09-26 12:51 ` [Buildroot] Buildroot nodejs 6.6.0 Martin Bark
2016-09-26 14:40 ` Jeroen Roovers
2016-09-26 14:48 ` Paul
2016-09-26 15:53 ` Martin Bark
2016-09-27 14:42 ` Paul
2016-09-26 19:45 ` Peter Korsgaard
2016-09-27 8:22 ` Martin Bark
2016-09-27 13:10 ` Thomas Petazzoni [this message]
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=20160927151038.474df7de@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