× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Wed, May 11, 2016 at 4:29 PM, Aaron Bartell <aaronbartell@xxxxxxxxx>
wrote:

Brian,

I am getting the same error. I have installed Node v4 and will IPL** later
tonight.

** Quite the inconvenience to IPL for PTFs that are fairly simple in nature
(though I could be completely ignorant here). There's got to be a better
way.

Best practice suggestion for others adopting open source langs on IBM i.
Use tar to save the lang directory and untar to a different one and operate
off that new directory.

--- These steps ~should~ be accurate :-) ---
$ node -v
0.12.9
$ cd /QOpenSys/QIBM/ProdData
$ tar -cvf /QOpenSys/node/node-0.12.9.tar Node/
$ cd /QOpenSys/node
$ tar -xvf /QOpenSys/node/node-0.12.9.tar

Then have a shell script to easily switch between versions.

----node_ver.sh----
export

PATH=/opt/freeware/bin:/QOpenSys/node/$1/Node/bin:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/bin
export LIBPATH=/QOpenSys/node/$1/Node/bin


And invoke it like this:

$ . node_ver.sh node-0.12.9


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


Good idea, Aaron.. but I think you need to do:

mkdir /QOpenSys/node

before the first tar. I'm just looking through what you're doing here and
it makes sense.. but my PATH variable looks nothing like what you have
there. :) We shall see. I'll probably mess things up.

Brad
www.bvstools.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.