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

[DSpeichert]

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]

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]

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]

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]

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