Go back to ~/.juliaup as the default install location #447
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts #329 because I think in hindsight that was a mistake and the original behavior was better.
The primary problem is that if we install Juliaup itself into
.julia
in the standalone case, we create his weird asymmetry to the cases where we use a system package manager to install Juliaup. In the latter case, Juliaup is going to be installed somewhere on the system that is package manager specific, i.e. Windows Store puts it somewhere, brew puts it somewhere else etc. Things will just be a heck of a lot easier if the content of.julia/juliaup
is always the same, regardless of how Juliaup itself was installed.Things that will be better:
JULIA_DEPOT
gets much cleaner. Juliaup right now respects that, except in the standalone version it doesn't use it for itself, which is super weird.Medium term my hope is that we can use system package managers for Juliaup itself on as many systems as possible and have the standalone version fade more and more into the background in any case.