Skip to content
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

Tell people not to use their package manager's "Julia" #2089

Merged
merged 1 commit into from
Apr 20, 2024

Conversation

LilithHafner
Copy link
Member

I just got off the phone with someone running into issues with Julia 1.7, recently installed courtesy of their package manager.

Copy link

Once the build has completed, you can preview your PR at this URL: https://julialang.netlify.app/previews/PR2089/ in ~15 minutes

Copy link
Member

@StefanKarpinski StefanKarpinski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might word it to more strongly emphasize that juliaup is recommended and also mentions that using your distro's juliaup package and then letting that install official Julia binaries is a fine way to go.

@LilithHafner
Copy link
Member Author

We already place Juliaup above the official binaries, and I don't want to do too much more than that given the state of https://github.com/JuliaLang/juliaup/milestone/7. If someone is deciding whether or not to use their distro's broken 1.7.1, official binaries and juliaup are both a bit step up.

As for juliaup via package managers/distros, I'm hesitant to recommend that given

Important note: As of now, we strongly recommend to install Juliaup via the Windows Store or curl command above rather than through OS-specific software repositories (see below) as the Juliaup variants provided by the latter currently have some drawbacks (that we hope to lift in the future).

https://github.com/JuliaLang/juliaup?tab=readme-ov-file#software-repositories

@StefanKarpinski
Copy link
Member

Ok, carry on then!

@LilithHafner LilithHafner merged commit bd14c61 into main Apr 20, 2024
3 checks passed
@LilithHafner LilithHafner deleted the LilithHafner-patch-1 branch April 20, 2024 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants