[Buildroot] [PATCH 3/3] package/nodejs: remove 0.10.x support

[Yann E. MORIN <yann.morin.1998@free.fr>]

Arnout, All,

On 2017-03-06 13:23 +0100, Arnout Vandecappelle spake thusly:
> On 06-03-17 11:08, Martin Bark wrote:
> > On 5 March 2017 at 22:40, Arnout Vandecappelle <arnout@mind.be
> > <mailto:arnout@mind.be>> wrote:
> > 
> > 
> > 
> >     On 05-03-17 00:48, Martin Bark wrote:
> >     > nodejs 0.10.x is now end of life and is no longer maintained so remove it.
> >     > See https://github.com/nodejs/LTS
> > 
> >      As mentioned in the Config.in:
> > 
> >     # Starting with 0.12.x, on ARM, V8 (the JS engine)
> >     # now requires an armv6+ and a VFPv2+.
> > 
> >      Some people opposed the removal of 0.10 because it would make nodejs
> >     unavailable on ARM9, while it is really still useful there. So the idea is that
> >     we keep it around in frozen state.
> > 
> > 
> > We have discussed this a few times.  The last email exchange i had on this
> > subject was back on 27th September 2016 where Thomas said
> > 
> > "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."
> > 
> > I purposefully held off submitting these patches until after the 2017.02 release
> > so that it included nodejs 0.10.x.  Personally i would like to see 0.10.x
> > dropped from buildroot.
> 
>  Ah, OK, I forgot about that bit :-)
> 
>  Peter/Thomas, perhaps add a link to
> http://lists.busybox.net/pipermail/buildroot/2016-September/173060.html and
> http://lists.busybox.net/pipermail/buildroot/2015-December/147109.html
> when committing?
> 
>  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.

Regards,
Yann E. MORIN.

>  I have one remaining gripe, however: ideally there should be a Config.in.legacy
> entry. But of course that's impossible because the BR2_PACKAGE_NODEJS symbol
> still exists... One extremely hacky solution would be to add
> BR2_PACKAGE_NODEJS_VERSION_STRING to Config.in.legacy, *with* a prompt and
> without the dependency on BR2_PACKAGE_NODEJS. Then, if someone updates with an
> existing .config, the previously-hidden VERSION_STRING will appear in the legacy
> menu. But that solution looks pretty hairy, and I'm sure that people will notice
> in other ways that nodejs has vanished, so it's probably not so important.
> 
>  Regards,
>  Arnout
> 
> -- 
> Arnout Vandecappelle                          arnout at mind be
> Senior Embedded Software Architect            +32-16-286500
> Essensium/Mind                                http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'