All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/5] package/nodejs: correct 0.10.x option name
Date: Fri, 18 Dec 2015 22:12:13 +0100	[thread overview]
Message-ID: <20151218211213.GD27578@free.fr> (raw)
In-Reply-To: <1450394426-3349-3-git-send-email-martin@barkynet.com>

Martin, All,

On 2015-12-17 23:20 +0000, Martin Bark spake thusly:
> 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

No, you can't select an option that is in a choice. All you can do in
this case is tell the user to check his configuration, and refer him
to the version choice.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-12-18 21:12 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 ` [Buildroot] [PATCH v2 3/5] package/nodejs: correct 0.10.x option name Martin Bark
2015-12-18 21:12   ` Yann E. MORIN [this message]
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=20151218211213.GD27578@free.fr \
    --to=yann.morin.1998@free.fr \
    --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.