Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of brian.leroux@gmail.com
 designates 209.85.223.175 as permitted sender)
MIME-Version: 1.0
Sender: brian.leroux@gmail.com
In-Reply-To: 
 <5900F9BCB827854FB01CA94BA718810D0D1D6D98@USPHLEMB11A.global.corp.sap>
References: 
 <CAEeRA4oi3pj6aJA9A0hSaHeca6iW3QpJDifUBAH8wFnKEV+7+A@mail.gmail.com>
	<CAESi+49rvdfrqf4J5hWMpYwZO2_pjP2w0m7ZSzdSMeSGcN_VtQ@mail.gmail.com>
	<CAEeRA4oNcw9vMVKUhAmdoTFNbUkErRcj8UFZ1dwGa1HHvsb1zA@mail.gmail.com>
	<5900F9BCB827854FB01CA94BA718810D0D1D6D98@USPHLEMB11A.global.corp.sap>
Date: Thu, 20 Jun 2013 15:06:27 -0700
Message-ID: 
 <CADVgkyP6zFJgzZ6hG7dBa6iUjdL+uqoD+kdS6pdVqyT=jkGfWQ@mail.gmail.com>
Subject: Re: BB10 bundling of node.js
From: Brian LeRoux <b@brian.io>
To: dev@cordova.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Node is not the problem. But different versions of Node is a problem.

On Thu, Jun 20, 2013 at 2:52 PM, Wargo, John <john.wargo@sap.com> wrote:
> The way the market is going, node becomes more and more common. I don't think it's inappropriate to expect node to be there (provided you tell them it's a requirement). It's already one for the CLI, right?
>
> John M. Wargo
> SAP | Charlotte, NC | USA
> Office: +1 704.321.0265 | Mobile: +1 704.249.7476
> Email: john.wargo@sap.com
> Twitter: @johnwargo
>
>
> -----Original Message-----
> From: Bryan Higgins [mailto:bryan@bryanhiggins.net]
> Sent: Wednesday, June 19, 2013 3:22 PM
> To: dev@cordova.apache.org
> Subject: Re: BB10 bundling of node.js
>
> So for Cordova 3.0 in general, users will be required to pre-install a
> minimum version of node globally?
>
> We have had issues where upgrading node breaks stuff. I'd like to avoid
> that and give users flexibility with their own system configuration.
>
>
> On Wed, Jun 19, 2013 at 3:09 PM, Gord Tanner <gtanner@gmail.com> wrote:
>
>> -1
>>
>> I would rather we just use the system version of node which would be the
>> same version as the CLI.  I can't think of any reason a specific platform
>> (aka BlackBerry) would need a special version of a common dependency.
>>
>> Also I don't think you can bundle binaries in an apache release.
>>
>>
>> On Wed, Jun 19, 2013 at 3:01 PM, Bryan Higgins <bhiggins@blackberry.com
>> >wrote:
>>
>> > I'd like to reopen the topic of bundling node js into the blackberry
>> > platform.
>> >
>> > I have personally gotten feedback from users of errors which were caused
>> by
>> > node version inconsistencies. We have since updated the check_req script
>> to
>> > test for the minimum version of node we require, but that is not an ideal
>> > solution since users may need a different node version installed globally
>> > for other software.
>> >
>> > At a minimum, I'd like to give users the option to point to an alternate
>> > version of node. I have logged a JIRA issue for that. [1]
>> >
>> > What I'd prefer to do, is bundle the node binaries into the distribution.
>> > That would completely eliminate the dependency. Users would only need to
>> > worry about setting up the native SDK.
>> >
>> > We already do this in the WebWorks SDK [2]
>> >
>> > I'm interested how the community feels about this. Are there any
>> licensing
>> > concerns in Apache hosting binaries without source?
>> >
>> > [1] https://issues.apache.org/jira/browse/CB-3798
>> > [2]
>> >
>> >
>> https://github.com/blackberry/BB10-Webworks-Packager/tree/master/third_party/node
>> >
>>