From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/nodejs: remove 0.10.x support
Date: Tue, 07 Mar 2017 16:32:11 +0100 [thread overview]
Message-ID: <87innlcdc4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170306211322.GD3976@free.fr> (Yann E. MORIN's message of "Mon, 6 Mar 2017 22:13:22 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>> Note that in that December 2015 thread, Yann suggested to keep 0.10
>> indefinitely, but everybody else seemed to agree with Martin's suggestion to
>> drop it.
> Well, my position at the time wwas that "As long as it builds and still
> works fine, we should just keep it."
> But now, 0.10.x is only for armv5. Do we really expect such a low-end
> system to run nodejs?
> I don't care much about maintaining 0.10.x, especially now since
> upstream compleely dropped support.
I also don't think we can realisticly support it longer term going
forward if upstream won't any more, so I'm ok with dropping it.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-03-07 15:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 23:48 [Buildroot] [PATCH 1/3] DEVELOPERS: add Martin Bark for package/nodejs Martin Bark
2017-03-04 23:48 ` [Buildroot] [PATCH 2/3] package/nodejs: bump version to 7.7.1 Martin Bark
2017-03-12 22:36 ` Thomas Petazzoni
2017-03-14 9:11 ` Martin Bark
2017-03-04 23:48 ` [Buildroot] [PATCH 3/3] package/nodejs: remove 0.10.x support Martin Bark
2017-03-05 22:40 ` Arnout Vandecappelle
2017-03-06 10:08 ` Martin Bark
2017-03-06 12:23 ` Arnout Vandecappelle
2017-03-06 21:13 ` Yann E. MORIN
2017-03-07 15:32 ` Peter Korsgaard [this message]
2017-03-05 11:13 ` [Buildroot] [PATCH 1/3] DEVELOPERS: add Martin Bark for package/nodejs Thomas Petazzoni
2017-03-05 15:35 ` Martin Bark
2017-03-05 15:49 ` Yann E. MORIN
2017-03-05 17:51 ` Thomas Petazzoni
2017-03-05 20:28 ` Martin Bark
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=87innlcdc4.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 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.