All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Bark <martin@barkynet.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot nodejs 6.6.0
Date: Tue, 27 Sep 2016 09:22:02 +0100	[thread overview]
Message-ID: <CAFGQKxcFTgyOWB+h84PgRCVpcpTRYe1q9XrJe3B+dVZAycu1oQ@mail.gmail.com> (raw)
In-Reply-To: <87zimu30ny.fsf@dell.be.48ers.dk>

On 26 September 2016 at 20:45, Peter Korsgaard <peter@korsgaard.com> wrote:

> >>>>> "Martin" == Martin Bark <martin@barkynet.com> writes:
>
>  > Paul,
>  > I've been busy on other work recently so I've not had the time to bump
> the
>  > node version in buildroot for a while.  I do have some patches lined up
> to
>  > bump node to 6.6.0, however, I've held off submitting them because
> 6.7.0 is
>  > due tomorrow (see
>  > https://nodejs.org/en/blog/vulnerability/september-2016-
> security-releases/).
>  > So i expect to submit some patches hopefully later this week to bump
> node
>  > to 6.7.0.
>
> 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.

Note: I'll submit patches to bump 6.x to 6.7.0 and 0.10.x to 0.10.47

Thanks

Martin


>
> --
> Bye, Peter Korsgaard
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160927/30a5fe67/attachment.html>

  reply	other threads:[~2016-09-27  8:22 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 [this message]
2016-09-27 13:10       ` Thomas Petazzoni

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=CAFGQKxcFTgyOWB+h84PgRCVpcpTRYe1q9XrJe3B+dVZAycu1oQ@mail.gmail.com \
    --to=martin@barkynet.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.