-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 <bhigg...@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 >
