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
installing juliaup through the sh script, and then symlinking the juliaup binary breaks correct autoreferentiality of the executable. let my_own_path = std::env::current_exe() does not follow symlinks (at least on macOS).
running juliaup self update incurs in
Error: Failed to update versions db.
Caused by:
0: `run_command_update_version_db` command failed to load configuration db.
1: Failed to open juliaup config file.
2: No such file or directory (os error 2)
running juliaup self uninstall will fail to correctly remove the paths.juliaupselfhome folder since it will point to two parent folders with respect to the symlink location instead of the true executable.
with the patched source (added some code to show the difference in the info command):
$ ./juliaup info <-- invoking the symlink
TEST:: current_exe: /Users/<user>/projects/juliaup_dev/juliaup <-- symlinked to the build output in target/debug
TEST:: canonicalised_exe: /Users/<user>/projects/juliaup_dev/target/debug/juliaup
The text was updated successfully, but these errors were encountered:
Hello,
installing
juliaup
through thesh
script, and then symlinking thejuliaup
binary breaks correct autoreferentiality of the executable.let my_own_path = std::env::current_exe()
does not follow symlinks (at least on macOS).running
juliaup self update
incurs inrunning
juliaup self uninstall
will fail to correctly remove thepaths.juliaupselfhome
folder since it will point to two parent folders with respect to the symlink location instead of the true executable.with the patched source (added some code to show the difference in the info command):
The text was updated successfully, but these errors were encountered: