Updating gpg key
In order to validate that the packages came from me, you'll want to install my public GPG key on your system.
You can take care of that with a single command: The preferred method of adding my repository to your RHEL or Cent OS system is with the Yum package manager.
First things first, all of my binaries are GPG signed.
That means that you can be sure that these packages are coming from me, even if you should happen to find them on some other site (if you find a file with "jason" in the name and it isn't signed, DON'T install it).
Oh, by the way, it should go without saying that if you are no longer using a pure RPM-based install of RHEL/Cent OS (meaning that you have rebuilt httpd, php, mysql, or any system libraries from source, or are using CPanel, or a similar management app that compiles components from source) then, at best, you're not going to get very far, and at worst, you'll break your server.
Like for example with the n-package not using the latest stable release.
Would you like to answer one of these unanswered questions instead?
MKVTool Nix uses packages from the Extra Packages for Enterprise Linux (EPEL) repository.
my 2c: I tried both with n and with nvm on Linux Ubuntu 12.04 LTS, in order to update node from v0.8.25 to v0.10.22.
The first one was successfully completed, but the command 'which node' resulted in the old v0.8.25.