Skip to content
New issue

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

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

Already on GitHub? # to your account

ln: /usr/local/opt/nvm/current: File exists #499

Closed
allaire opened this issue Aug 15, 2014 · 5 comments
Closed

ln: /usr/local/opt/nvm/current: File exists #499

allaire opened this issue Aug 15, 2014 · 5 comments
Assignees
Labels
bugs Oh no, something's broken :-(
Milestone

Comments

@allaire
Copy link

allaire commented Aug 15, 2014

I get this message when I open iTerm on my Mac. I open multiple terminal at the same time, so maybe they all try to ln at the same time?

@ljharb
Copy link
Member

ljharb commented Aug 15, 2014

Gotta love race conditions. That's entirely likely - thanks, we'll look into it.

@ljharb ljharb added the bugs label Aug 15, 2014
@ljharb
Copy link
Member

ljharb commented Aug 19, 2014

@koenpunt It occurs to me that since nvm usage is shell-specific, the current symlink is kind of meaningless. Perhaps it was a mistake to add it?

@koenpunt
Copy link
Contributor

Could be, I never voted for it anyway.. But I'm currently on vacation. The only symlinks that can be of use are those of aliases.

@ljharb
Copy link
Member

ljharb commented Aug 30, 2014

#514 adds an env var, NVM_SYMLINK_CURRENT, that when set, and set to anything but "true", will not create the symlink.

In the near future, I'll change the default behavior of this env var from "unset" => "true" to "unset" => "false".

@ljharb ljharb added this to the v1.0.0 milestone Oct 7, 2014
@ljharb ljharb self-assigned this Oct 15, 2014
@ljharb ljharb added feature requests I want a new feature in nvm! needs followup We need some info or action from whoever filed this issue/PR. bugs Oh no, something's broken :-( and removed bugs Oh no, something's broken :-( feature requests I want a new feature in nvm! needs followup We need some info or action from whoever filed this issue/PR. labels Oct 15, 2014
@ljharb ljharb closed this as completed in ca89cce Oct 15, 2014
@ljharb
Copy link
Member

ljharb commented Oct 15, 2014

This will be fixed in the next release; specifically by disabling the symlink behavior. It can be opted into via setting the NVM_SYMLINK_CURRENT environment variable to "true".

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bugs Oh no, something's broken :-(
Projects
None yet
Development

No branches or pull requests

3 participants