I’m aware of four systems for Julia version management: | Manual | jill | UpdateJulia | juliaup | juliavm status | official | stable | stable | stable / known bugs | stable? version multiplexing | N/A | no…

[image] DNF: You can switch between Julia versions with Juliaup too. I know. [image] DNF: I’m not sure what this means. I mean, I don’t want any integration into my OS, like setting PATH variables or whatever is needed. So, for me, despite knowing about juliaup’s features, I like to …

To clarify a bit: I knew of, but only alluded to, the implementation language history of juliaup. rust is clearly the winner there, especially since the (volunteer) developers are very enthusiastic about the choice. There may be some people who think that a standard installer should be written in Py…

BTW: I find the experience with portable Julia superior to the alternative (installer)! Especially in combination with a custom depot. See Portable Julia - #16 by PetrKryslUCSD Edit: try it with Julia 1.7.1.

@carstenbauer Thanks! I’ve removed “rust?” pardon my ignorance that rust compiles to standalone executables. According to the juliaup readme , “On all platforms it is recommended that you first uninstall any previous Julia versions and undo any modifications you might have made to put Julia on the P…

Perhaps this is a silly question, but are we reinventing the wheel by writing our own multiplexer in rust instead of using the operating system’s default behavior via symlinks and path environment variables? For example, on my machine I have julia-1.6.4, julia-1.6.5, julia-1.7.1, julia-1.7.2, etc. …

[image] Lilith: with ln , stop thinking in Linux, although I only use Linux, but if you want Julia to be universally accessible reinventing some wheels is no big deal, it’s not like we’re going to pile on top of juliaup and having breaking release every month, it’s just an end users’ tool, th…

Not a silly question. But, I think symlinks and environment variables are kind of a mess to work with. People (eg linux distros) tend to write utils with APIs to manage them. And the multiplexer is already written. Having a single API is great for help/documentation/cognitive load. Otherwise each …

[image] jlapeyre: I think “recommended that you first uninstall” is to avoid problems for the uninitiated. Yes, that is correct. I just don’t want to deal with support requests when folks end up having two julia things on their PATH :slight_smile: But as long as someone sorts that out properl…

I don’t think the dispatcher julia from juliaup is identical to using symlinks. There might be a super useful feature in the near future where, if the project is known at startup time, you can dispatch to the appropriate (compatible) julia version. This is from my point of view a killer feature that…

Might make sense to have an “Advanced installation” section that explains what someone who is comfortable with more manual stuff can do.

Plans for Updating Julia

Tooling

Topic		Replies	Views
Juliaup: a modest suggestion Internals & Design	62	3449	May 4, 2025
`juliaup` for for Mac and Linux Tooling linux , juliaup	28	4055	October 15, 2024
[ANN] Juliaup Preview - Julia version manager and Windows Store installer Community announcement , juliaup	94	12572	March 13, 2022
A graphical Julia installer for Windows General Usage windows	48	2675	August 4, 2025
Why is juliaup emphasized as the installation mechanism? Tooling	60	2831	February 5, 2026

Plans for Updating Julia

Related topics