You can clone with
HTTPS or Subversion.
Don't put stuff directly in /usr/local.
Liberal use of hash -r whenever the PATH changes, and respect JOBS env
README.md: Update Usage to the latest help information
Add NAVE_DEBUG, and use ~/.nave instead of the nave dir
add a check when 'nave use' is called with no args
rough sketch of named envs
In a separate command for now. Should merge "use" and "named" into just
"use", and have it be smart enough to know that anything not matching a
release version, "latest" or "stable" is a named env.
Set npm configs and NODE_PATH in the env.
bump version, add Marco to contribs
always build debug enabled node too
typo, bump version
Support "stable" as a shorthand for "latest 0.2.x"
Bump version to 0.0.7 and add Kai Chen => 陈恺 to contributor list.
fix the path issue
Respect the TAR env, if set
Fetch from the old-style URLs if the new-style one fails, and call ta…
…r such that it works with FreeBSD
Add support for 'latest' as a version string
Add the nave use <ver> <prog> to help/README
Add usemain, since TJ asked so nice, and it actually is quite handy.
double-listed the 'install' command
Refactor ls-* functions to all use the same sort, and to sort and pre…
…ttify the output.
Remove the HEAD stuff. That's what git is for.
ls-remote: Just do the uniq-ing in the sort command
Bump version, add TJ to contributors
Show the old versions also, and sort by version number.
ls-remote using nodejs.org/dist
Less verbose install