with '' will be ignored, and an empty message aborts the commit.
On branch master
Your branch is up to date with 'origin/master'.
Changes to be committed:
new file: .github/__init__.py
new file: .github/workflows/__init__.py
new file: .vscode/__init__.py
new file: __init__.py
new file: test/__init__.py
new file: test/fast/Aliases/__init__.py
new file: test/fast/Aliases/circular/__init__.py
new file: test/fast/Aliases/lts/__init__.py
new file: test/fast/Listing paths/__init__.py
new file: test/fast/Listing versions/__init__.py
new file: test/fast/Set Colors/__init__.py
new file: test/fast/Unit tests/__init__.py
new file: test/fast/Unit tests/mocks/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/inside-n_m-nested-pkg/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/inside-n_m-nested/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-both/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-both/a/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-both/a/b/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-both/a/b/c/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-both/a/b/c/d/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-n_m/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-n_m/a/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-n_m/a/b/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-n_m/a/b/c/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-n_m/a/b/c/d/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-pkg/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-pkg/a/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-pkg/a/b/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-pkg/a/b/c/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-pkg/a/b/c/d/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/no-nesting-both/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/no-nesting-n_m/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/no-nesting-pkg/__init__.py
new file: test/fast/__init__.py
new file: test/install_script/__init__.py
new file: test/installation_iojs/__init__.py
new file: test/installation_node/__init__.py
new file: test/mocks/__init__.py
new file: test/slow/__init__.py
new file: test/slow/nvm exec/__init__.py
new file: test/slow/nvm reinstall-packages/__init__.py
new file: test/slow/nvm reinstall-packages/test-npmlink/__init__.py
new file: test/slow/nvm run/__init__.py
new file: test/slow/nvm uninstall/__init__.py
new file: test/slow/nvm use/__init__.py
new file: test/slow/nvm_get_latest/__init__.py
new file: test/sourcing/__init__.py
new file: test/xenial/__init__.py
On SmartOS setups using 64 bits pkgsrc repositories, `nvm_get_arch`
would not handle pkg_info's output properly.
This would result in nvm not being to install any node binary when
running on SmartOS setups using a 64 bits pkgsrc repository.
This change fixes this problem, and fixes the tests suite on similar
setups.
uname on SmartOS cannot be used to guess if 32 and/or 64 bits binaries
are supported, and its output is different than other uname commands on
other operating systems.
This change uses pkg_info to determine what types of binaries pkgsrc
would install. If pkg_info fails to run or is not present, this change
falls back to using isainfo -n, which determines what the kernel
supports.
It allows users to install node binaries on Solaris derivatives. io.js
can also be installed on Solaris derivatives starting with version
v3.3.1.
