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

Improve (or eliminate) error when you run post-0.9.0 meteor from a symlink or alias #2462

Closed
DSpeichert opened this issue Aug 28, 2014 · 4 comments

Comments

@DSpeichert
Copy link

Running curl https://install.meteor.com/ | sh is fine. then running meteor:

/home/dd/.meteor/meteor: line 124: /home/dd/.meteor/dev_bundle/bin/node: No such file or directory

There is no ~/.meteor/dev_bundle directory, nor ~/.meteor/tools/main.js (which should be ran).

Is there some bug with the installation procedure?

@glasser
Copy link
Contributor

glasser commented Aug 28, 2014

Hmm, that file is not expected to exist. What does

type -a meteor

tell you? And can you post the contents of your /usr/local/bin/meteor file somewhere, maybe a gist?

@DSpeichert
Copy link
Author

So, before I answer your questions, I figured out a couple of things.
If I move /usr/local/bin/meteor to ~/bin/meteor (bin is in my PATH), then it doesn't work - error as above.
Same happens when setting an alias meteor="/home/user/.meteor/meteor".
However, when I use the binary from /usr/local/bin/meteor it works fine.

@glasser
Copy link
Contributor

glasser commented Aug 28, 2014

Adding ~/.meteor to your PATH works too. Our install script (http://install.meteor.com/) doesn't actually suggest that you use an alias any more.

@DSpeichert
Copy link
Author

Yes. I think it should fail with a more meaningful error when ran symlinked or from a weird path (if it needs to fail).

@glasser glasser changed the title Problem installing new Meteor 0.9.0.1 Improve (or eliminate) error when you run post-0.9.0 meteor from a symlink or alias Sep 2, 2014
@glasser glasser closed this as completed in c1baf7a Sep 2, 2014
glasser added a commit that referenced this issue Sep 5, 2014
Fixes #2462.

Too bad we can't just access realpath somehow...
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

No branches or pull requests

2 participants