-
Notifications
You must be signed in to change notification settings - Fork 92
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
Symlinked path doesn't point to correct location #7
Comments
morganestes
added a commit
to morganestes/asimov
that referenced
this issue
Nov 14, 2017
Switch to using `pwd` for absolute paths instead of the relative path generated by `dirname $0`. Longer description about what and why, if it's needed. Don't be afraid to be verbose as necessary, and don't go longer than 72 chars per line.
stevegrunwell
added a commit
that referenced
this issue
Nov 24, 2017
Rather than relying on `$(dirname "$0")` or `$(pwd)`, which can have issues with relative paths (e.g. "./install.sh") or the user's current working directory, respectively), this approach literally changes into the script directory to get the full directory. Based on https://stackoverflow.com/a/4774063/329911. Fixes #7 and closes #8. Props @morganestes.
Morgan, as usual:
Happy Thanksgiving! 🦃 |
Thanks for creating and sharing some great tools! No worries about timing, it's yours to do with as you see fit, and mine to use and suggest. :smiling: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I run
install.sh
, the directory gets declared as.
, resulting in a symlink path of./asimov
inside/usr/local/bin
. This causes the script to fail as it can't find the correct path of the executable inside the repo.Changing to
$(pwd)
inside the installer fixes this, so the symlink points to the full path and not the relative one.The text was updated successfully, but these errors were encountered: