Re: [IBMiOSS] gmake: *** virtual memory exhausted. Stop.

I wouldn't expect Node 0.12.10 -> 0.12.11 to be a problematic upgrade, but

maybe I'm naive.

As I understand it, Node.js proper has adopted the io.js semver.org
decision, so in theory everything for x (0.12.x) should be non-detrimental
(no API signature changes, no change in results, etc). But there are
additional things that need attention on the IBM i side of things(n1).
Before I adopt the fix of the thing that needed attention I want to install
it to make sure it is in fact fixed.

Some history for anybody that wants it:
https://nodesource.com/blog/nodejs-is-semver

n1 - Node.js PTFs for the same version (Node.js version is not incremented
because it was an IBM i specific issue): http://bit.ly/dw-nodejs-ptf

Aaron Bartell
litmis.com - Services for open source on IBM i


On Wed, Jul 20, 2016 at 1:12 PM, Kevin Adler <kadler@xxxxxxxxxx> wrote:

"OpenSource" <opensource-bounces@xxxxxxxxxxxx> wrote on 07/20/2016
12:42:30 PM:

From: Aaron Bartell <aaronbartell@xxxxxxxxx>
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Date: 07/20/2016 12:43 PM
Subject: Re: [IBMiOSS] gmake: *** virtual memory exhausted. Stop.
Sent by: "OpenSource" <opensource-bounces@xxxxxxxxxxxx>

I would think then you wouldn't have to worry much about updates to

Node

itself.

Multiple versions are still necessary because language features are
changing. For example, I might install the latest PTF with the new

Node.js

version but I don't want to blindly accept the PTF won't cause issues

with

my existing app. I would instead want to run all of my unit tests

against

the new version without losing the old version. There's just too many
things that could go wrong (i.e. a deprecated API warning coming to full
fruition and is finally removed).

Right, but don't these sort of changes only happen going from eg. 1.x ->
2.x (in OPS these would be in separate options).

I wouldn't expect Node 0.12.10 -> 0.12.11 to be a problematic upgrade, but
maybe I'm naive.

--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.