Closed Mistress-Anna closed 6 years ago
@Mistress-Anna I've updated package.json
to use the $npm_node_execpath
. I was then able to successfully perform npm install
on Debian 8:
cody@80f4124a-b0a5-cea5-9145-955ca04c694d:~/node-dtrace-provider$ V=1 npm install
> dtrace-provider@0.8.4 install /home/cody/node-dtrace-provider
> $npm_node_execpath scripts/install.js
cody@80f4124a-b0a5-cea5-9145-955ca04c694d:~/node-dtrace-provider$ node --version
-su: node: command not found
cody@80f4124a-b0a5-cea5-9145-955ca04c694d:~/node-dtrace-provider$ nodejs --version
v0.10.29
cody@80f4124a-b0a5-cea5-9145-955ca04c694d:~/node-dtrace-provider$ npm version
{ http_parser: '1.0',
node: '0.10.29',
v8: '3.14.5.8',
ares: '1.10.0',
uv: '0.10.27',
zlib: '1.2.8',
modules: '11',
openssl: '1.0.1k',
npm: '1.4.21',
'dtrace-provider': '0.8.4' }
These changes are now on npm in version 0.8.4
.
I've reverted these changes since they break installing on Windows. I can't find a good solution for supporting installation in both environments that use different syntax for environment variables and have differently named binaries, so for now users with different binary names will need to set up symbolic links or wrapper scripts and their PATH
appropriately. (Some Debian systems also ship the node-legacy
package, which seems to be the same as the nodejs
package but it creates a node
binary instead of nodejs
.)
With dtrace-provider@0.8.6
, as long as the dependencies for running node-gyp
are present (GNU Make and Python 2), installing on Debian should no longer be an issue.
On Debian, "node" command is "nodejs", because the "node" command conflicts with other packages.