From: Martin Bark <martin@barkynet.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/5] package/nodejs: correct 0.10.x option name
Date: Thu, 17 Dec 2015 23:20:24 +0000 [thread overview]
Message-ID: <1450394426-3349-3-git-send-email-martin@barkynet.com> (raw)
In-Reply-To: <1450394426-3349-1-git-send-email-martin@barkynet.com>
The nodejs options incorrectly started BR2_BR2_xxx. This change corrects
the name for 0.10.x releases to BR2_PACKAGE_NODEJS_0_10_X
Signed-off-by: Martin Bark <martin@barkynet.com>
---
Changes v1 -> v2
- New in v2
---
Config.in.legacy | 8 ++++++++
package/nodejs/Config.in | 6 +++---
2 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/Config.in.legacy b/Config.in.legacy
index db1eeae..5d9a3ee 100644
--- a/Config.in.legacy
+++ b/Config.in.legacy
@@ -186,6 +186,14 @@ config BR2_PACKAGE_INFOZIP
to avoid ambiguities with Info-Zip's UnZip which has been added
in the unzip package.
+config BR2_BR2_PACKAGE_NODEJS_0_10_X
+ bool "nodejs 0.10.x option renamed"
+ select BR2_LEGACY
+ select BR2_PACKAGE_NODEJS_0_10_X
+ help
+ nodejs 0.10.x option was named incorrectly and been renamed
+ to BR2_PACKAGE_NODEJS_0_10_X.
+
config BR2_BR2_PACKAGE_NODEJS_0_12_X
bool "nodejs version 0.12.x has been removed"
select BR2_LEGACY
diff --git a/package/nodejs/Config.in b/package/nodejs/Config.in
index cba320c..5d776d7 100644
--- a/package/nodejs/Config.in
+++ b/package/nodejs/Config.in
@@ -36,12 +36,12 @@ config BR2_PACKAGE_NODEJS_V8_ARCH_SUPPORTS
choice
prompt "Node.js version"
- default BR2_BR2_PACKAGE_NODEJS_0_10_X if BR2_ARM_CPU_ARMV5
+ default BR2_PACKAGE_NODEJS_0_10_X if BR2_ARM_CPU_ARMV5
default BR2_PACKAGE_NODEJS_5_X
help
Select the version of Node.js you wish to use.
-config BR2_BR2_PACKAGE_NODEJS_0_10_X
+config BR2_PACKAGE_NODEJS_0_10_X
bool "v0.10.41"
config BR2_PACKAGE_NODEJS_5_X
@@ -59,7 +59,7 @@ endchoice
config BR2_PACKAGE_NODEJS_VERSION_STRING
string
- default "0.10.41" if BR2_BR2_PACKAGE_NODEJS_0_10_X
+ default "0.10.41" if BR2_PACKAGE_NODEJS_0_10_X
default "5.3.0" if BR2_PACKAGE_NODEJS_5_X
menu "Module Selection"
--
2.5.0
next prev parent reply other threads:[~2015-12-17 23:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 23:20 [Buildroot] [PATCH v2 1/5] package/nodejs: bump version to 5.3.0 Martin Bark
2015-12-17 23:20 ` [Buildroot] [PATCH v2 2/5] package/nodejs: removed version 0.12.9 Martin Bark
2015-12-17 23:20 ` Martin Bark [this message]
2015-12-18 21:12 ` [Buildroot] [PATCH v2 3/5] package/nodejs: correct 0.10.x option name Yann E. MORIN
2015-12-18 22:47 ` Arnout Vandecappelle
2015-12-20 17:03 ` Martin Bark
2015-12-17 23:20 ` [Buildroot] [PATCH v2 4/5] package/nodejs: fix support for uClibc-ng Martin Bark
2015-12-18 21:15 ` Yann E. MORIN
2015-12-20 16:58 ` Martin Bark
2015-12-17 23:20 ` [Buildroot] [PATCH v2 5/5] package/libuv: " Martin Bark
2015-12-18 21:09 ` [Buildroot] [PATCH v2 1/5] package/nodejs: bump version to 5.3.0 Yann E. MORIN
2015-12-18 21:35 ` Yann E. MORIN
2015-12-20 16:59 ` 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=1450394426-3349-3-git-send-email-martin@barkynet.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.