In other words, the old version is "hard coded" to be used unless you
tell
it otherwise through a script?
It's not really hard coded. When you specify a program without fully
qualifying it, the system will use the PATH environment variable to
determine which program to use.
so you run:
# node -v
and it will look through each segment of the PATH (separated by colons)
and see if a node executable exists in that location, stopping at the
first one found.
eg. in this order by default:
/QOpenSys/usr/bin/node
/usr/ccs/bin/node
/QOpenSys/usr/bin/X11/node
/usr/sbin/node
./node
/usr/bin/node
OPS option 1 shipped a symlink in /QOpenSys/usr/bin/node which points to
/QOpenSys/QIBM/ProdData/Node/bin/node, so that is found first. If you want
a different "node" to be found, you must either fully qualify the path or
change the PATH so that the one you want is found first.
Only one option can own the /QOpenSys/usr/bin/node symlink, so option 5
can't change it to V4 (it could, but might get overwritten if you apply an
option 1 PTF or would get removed if you uninstall option 1, etc...).
On Linux and similar platforms, there's update-alternatives which keeps a
"database" of alternate versions of various utilities and sets up
symlinks. It lets the system install multiple versions and allow the user
to manage the symlinks. I'd like to be able to ship something similar with
OPS in the future, but it doesn't exist currently.
Is there a place I can put a shell script to do this automatically every
time I start a terminal session?
See my previous message to the list on how to do this.
midrange.com
