Installing node with apt-get breaks existing batch scripts #1434

Closed
Jermolene opened this Issue Jan 28, 2015 · 6 comments

Projects

None yet

5 participants

@Jermolene
Owner

Using apt-get to install Node.js and npm (with sudo apt-get install nodejs npm) results in the Node executable being called nodejs. This means that the existing documentation and batch files won't work without modification.

@Jermolene Jermolene added the bug label Jan 28, 2015
@roma0104
Contributor

@Jermolene I am not sure if this is a bug. More of an inconvenience cause by distro package managers. It affects almost all Debian based distros and is a binary naming conflict between the nodejs package and this extremely niche package: https://packages.debian.org/wheezy/node

ArchLinux names the binary node
And if I remember right from my last foray, so does Gentoo.

Fedora and OpenSuse I am not certain... their package databases are terrible. (Which is not surprising having personally ventured to the hell of their package managers.)

Not sure what you stance would be, but we could sticky a note in build notes that suggests creating a symbolic link: sudo ln -s /usr/bin/nodejs /usr/bin/node, which I personally do, or simply point this out to the users. Unless the user happens to be a ham radio buff too I think the conflict would be limited.

@Jermolene
Owner

Not sure what you stance would be, but we could sticky a note in build notes that suggests creating a symbolic link: sudo ln -s /usr/bin/nodejs /usr/bin/node, which I personally do, or simply point this out to the users.

Good idea. Would you like to send a pull request for mods to Installing TiddlyWiki on Node.js?

@roma0104 roma0104 added a commit to roma0104/TiddlyWiki5 that referenced this issue Apr 25, 2015
@roma0104 roma0104 Updated to help notify user of #1434 13df1b6
@roma0104 roma0104 added a commit to roma0104/TiddlyWiki5 that referenced this issue Apr 28, 2015
@roma0104 roma0104 Added text notifying users of issue #1434 f9c50d9
@tobibeer
Contributor

Apart form the above docs, will there be anything else being done on this issue? It's a bit odd to see the commits but not a PR. Anyway, can this be closed?

@pmario
Contributor
pmario commented Sep 21, 2015

We can see the commits, because the issue number was mentioned in the commit message. may be no PR was done or the merge didn't close this issue.

@Jermolene
Owner

This was merged from #1685

@Jermolene Jermolene closed this Sep 22, 2015
@chronitis

Apologies for resurrecting a long-closed issue, but it is worth noting that Debian/Ubuntu provide a package nodejs-legacy which exists only to create the /usr/bin/node -> /usr/bin/nodejs symlink noted here. It's probably easier to tell people to install that than need to manually create the link.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment