All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] package/nodejs: Update to allow selecting node.js version
Date: Sun, 14 Jun 2015 22:53:09 +0200	[thread overview]
Message-ID: <20150614225309.07f354ed@free-electrons.com> (raw)
In-Reply-To: <1434298376-31893-1-git-send-email-martin@barkynet.com>

Dear Martin Bark,

On Sun, 14 Jun 2015 17:12:53 +0100, Martin Bark wrote:
> Signed-off-by: Martin Bark <martin@barkynet.com>

What is the motivation for supporting more than one version of NodeJS
at a time?

We generally try to avoid supporting multiple versions of a given
component, unless there are some really good reasons to do so (like
python2 vs. python3, or qt4 vs. qt5).

Thanks,

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

  parent reply	other threads:[~2015-06-14 20:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 16:12 [Buildroot] [PATCH 1/4] package/nodejs: Update to allow selecting node.js version Martin Bark
2015-06-14 16:12 ` [Buildroot] [PATCH 2/4] package/nodejs: Add node.js v0.12.4 and set as the default version Martin Bark
2015-06-14 16:12 ` [Buildroot] [PATCH 3/4] package/nodejs: Add global node_module to the PATH Martin Bark
2015-06-14 16:12 ` [Buildroot] [PATCH 4/4] package/nodejs: Define NPM command for other packages to use Martin Bark
2015-06-14 20:53 ` Thomas Petazzoni [this message]
2015-06-15  7:38   ` [Buildroot] [PATCH 1/4] package/nodejs: Update to allow selecting node.js version Jörg Krause
2015-06-16  9:56     ` 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=20150614225309.07f354ed@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 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.