Permalink
Browse files

Update install.sh

$HOME/.nvm used instead of introduced earlier NVM_TARGET.
  • Loading branch information...
1 parent 59c8eda commit 2f6b0ca9d733832e0ee9c8761ed0d63ba4a150f4 @witoldsz witoldsz committed Dec 4, 2012
Showing with 1 addition and 1 deletion.
  1. +1 −1 install.sh
View
@@ -25,7 +25,7 @@ else
fi
fi
-SOURCE_STR='[[ -s "$HOME/.nvm/nvm.sh" ]] && . "$HOME/.nvm/nvm.sh" # This loads NVM'
+SOURCE_STR='[[ -s "$NVM_TARGET/nvm.sh" ]] && . "$NVM_TARGET/nvm.sh" # This loads NVM'
@koenpunt
koenpunt Dec 4, 2012

$NVM_TARGET does not expand to the variable set in the script, so the line appears as following in your profile:

[[ -s "$NVM_TARGET/nvm.sh" ]] && . "$NVM_TARGET/nvm.sh" # This loads NVM
if [ -z "$PROFILE" ] || [ ! -f "$PROFILE" ] ; then
if [ -z $PROFILE ]; then

1 comment on commit 2f6b0ca

@witoldsz

Ah, of course, you are right.
I was thinking, maybe the NVM_TARGET should be assigned only when it is unset. That would allow users to launch install script with NVM_TARGET being preset to location of their own... or... the install location could be the parameter of the script.

Please sign in to comment.