You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
macOS automatically adds binaries in /usr/bin to PATH. Our install.sh script moves our built ally binary to that location - thus, the first line of the ally file ends up being:
alias ally="ally"
We should either fix this alias (i.e. not add it) or add an option to not add it or install in a different location.
Output
alias ally="ally"
THIS IS EXPECTED BEHAVIOR. This is also desired, as if the user installs in a location not on PATH, then we want this alias. We could fix it:
FIX
One, allow the user to specify --no-alias and also --overwrite (the second one is unrelated to this issue, but still good-to-have) when installing. Specify this --no-alias when calling ally init (which we might want to change to ally setup) from the script.
The text was updated successfully, but these errors were encountered:
Describe the bug
macOS automatically adds binaries in
/usr/bin
to PATH. Ourinstall.sh
script moves our built ally binary to that location - thus, the first line of the ally file ends up being:We should either fix this alias (i.e. not add it) or add an option to not add it or install in a different location.
Output
THIS IS EXPECTED BEHAVIOR. This is also desired, as if the user installs in a location not on PATH, then we want this alias. We could fix it:
FIX
One, allow the user to specify
--no-alias
and also--overwrite
(the second one is unrelated to this issue, but still good-to-have) when installing. Specify this--no-alias
when callingally init
(which we might want to change toally setup
) from the script.The text was updated successfully, but these errors were encountered: