Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make symlink to /usr/local/bin/node optional on OSX installer #389

Closed
mmarcon opened this issue Jan 14, 2015 · 10 comments
Closed

Make symlink to /usr/local/bin/node optional on OSX installer #389

mmarcon opened this issue Jan 14, 2015 · 10 comments
Labels
feature request Issues that request new features to be added to Node.js. install Issues and PRs related to the installers. macos Issues and PRs related to the macOS platform / OSX.

Comments

@mmarcon
Copy link

mmarcon commented Jan 14, 2015

In order to be able to run node and io.js in parallel and easily choose what to run, it would be nice if the OSX installer did not automatically create a symlink in /usr/local/bin/node.
@fhemberger
Copy link
Contributor

+1, if you've installed node via homebrew, you can symlink the node binary again, but if you've used the official node.js installer, your binary is overwritten by the symlink.

Symlinking should be an optional checkbox during the installation process.

@fampinheiro
Copy link

The symlink cannot be optional if you want to use npm #249

@Pana
Copy link

Pana commented Jan 14, 2015

It seems npm should add support for iojs

@h2non
Copy link

h2non commented Jan 14, 2015

Agree! I think it's a bit intrusive create an implicit symlink without asking

@kfranqueiro kfranqueiro mentioned this issue Jan 14, 2015
Closed
@bnoordhuis
Copy link
Member

I don't know if homebrew applies any special sauce but just skipping the symlink normally isn't enough to make joyent/node and io.js coexist, all the stuff that is installed to $prefix/share, $prefix/include/node, etc. conflicts. You have to install them to separate directories.

@bnoordhuis bnoordhuis added the install Issues and PRs related to the installers. label Jan 14, 2015
@nacholibre
Copy link

This will answer your question #631

People think (and I was too) that iojs is different from node, but its just newer version of node, so if you want to install new version of node without breaking your current one, just use nvm.

@benpptung
Copy link

@nacholibre Thank you very much :) I'd suggest to put this information on FAQ, because the first thing coming to my mind is not how to install io.js, but how to switch between io.js and node.js. Don't know nvm can do that, I am always using n and I see @caitp in #631 mention "...NVM is pretty terrible, it's a pain in the ass..." lol . Thank you again :)

@Florian-R Florian-R mentioned this issue Feb 11, 2015
Closed
@jdduncan
Copy link

"The symlink cannot be optional if you want to use npm".
Fair enough: I don't want to use npm. I'm doing development, not production. I want to test my code (including not just javascript, but also compiled native code) with io.js.

@Fishrock123
Copy link
Member

@jdduncan for development it is probably more useful overall to just use nvm -- that way you can also update easily, and switch between any node / io.js version.

@fhemberger fhemberger mentioned this issue Mar 17, 2015
Closed
@silverwind silverwind added the macos Issues and PRs related to the macOS platform / OSX. label Jul 13, 2015
@brendanashworth brendanashworth added the feature request Issues that request new features to be added to Node.js. label Jul 18, 2015
@Qard
Copy link
Member

Qard commented Aug 14, 2015

Closing as this is no longer relevant post-convergence.

@Qard Qard closed this as completed Aug 14, 2015
kapouer added a commit to kapouer/node that referenced this issue Apr 28, 2018
@kapouer
doc: fix manpage warning
a9618c1 
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z ./doc/node.1 > /dev/null
mdoc warning: Empty input line nodejs#389
@kapouer kapouer mentioned this issue Apr 28, 2018
Closed
addaleax pushed a commit that referenced this issue May 5, 2018
@kapouer @addaleax
doc: fix manpage warning
c6a4286 
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z ./doc/node.1 > /dev/null
mdoc warning: Empty input line #389

PR-URL: #20383
Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
MylesBorins pushed a commit that referenced this issue May 8, 2018
@kapouer @MylesBorins
doc: fix manpage warning
34f73ec 
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z ./doc/node.1 > /dev/null
mdoc warning: Empty input line #389

PR-URL: #20383
Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
MylesBorins pushed a commit that referenced this issue May 8, 2018
@kapouer @MylesBorins
doc: fix manpage warning
a5ba30b 
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z ./doc/node.1 > /dev/null
mdoc warning: Empty input line #389

PR-URL: #20383
Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
MylesBorins pushed a commit that referenced this issue May 9, 2018
@kapouer @MylesBorins
doc: fix manpage warning
79e1260 
LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 -Z ./doc/node.1 > /dev/null
mdoc warning: Empty input line #389

PR-URL: #20383
Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
@NOUIY NOUIY mentioned this issue Sep 10, 2022
Open
This was referenced Feb 10, 2023
Open
Open
@Dixiejane Dixiejane mentioned this issue Feb 14, 2023
Open
@nicholaschoi168 nicholaschoi168 mentioned this issue May 8, 2023
Merged
@snyk-bot snyk-bot mentioned this issue Jun 1, 2023
Open
@NOUIY NOUIY mentioned this issue Jun 1, 2023
Open
@Fsub111 Fsub111 mentioned this issue Feb 1, 2024
Open
@08epouu1 08epouu1 mentioned this issue Mar 16, 2024
Open
@ZRDK ZRDK mentioned this issue May 7, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request Issues that request new features to be added to Node.js. install Issues and PRs related to the installers. macos Issues and PRs related to the macOS platform / OSX.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests