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.

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

Use symlinks instead of copying files upon switch #85

Merged
merged 1 commit into from
Sep 30, 2012
Merged

Use symlinks instead of copying files upon switch #85

merged 1 commit into from
Sep 30, 2012

Conversation

Suor
Copy link
Contributor

@Suor Suor commented Sep 30, 2012

Backward incompatible change - any modules and executables
such as npm, coffee and even n itself are now different
for different node versions.

This is probably a good thing anyway. At least you won't get something like
"npm won't work with your node 0.8.11, install 0.6, please"

Bakward incompatable change - any modules and executables
such as npm, coffee and even n itself are now diffrent
for diffrent node versions. This is probably a good thing anyway.
tj added a commit that referenced this pull request Sep 30, 2012
Use symlinks instead of copying files upon switch
@tj tj merged commit 77946bb into tj:master Sep 30, 2012
&& cp -fR $dir/lib/node/* $N_PREFIX/lib/node/ .
# symlink everything, purge old copies or symlinks
for d in bin lib share include; do
rm -rf $N_PREFIX/$d
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#86

@benatkin
Copy link
Collaborator

benatkin commented Oct 8, 2012

I think the README should be changed to link to the npm tarball, instead of suggesting installing it from git. This bad commit isn't in npm.

@tj
Copy link
Owner

tj commented Oct 8, 2012

this project is kinda in limbo i wont lie haha, i dont have time to properly review things :( a maintainer would be fantastic

@benatkin
Copy link
Collaborator

benatkin commented Oct 8, 2012

In the mean time please just do git revert HEAD and git push

@benatkin
Copy link
Collaborator

benatkin commented Oct 8, 2012

Or instead use this commit ID...head might be a merge commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants