Installation has gotten worse

Installing Julia used to be easier; it used to work like every other “app” on my Mac. Now, I’m asked to copy/paste some command (no explanation on the options on that command, isn’t it bad form to train users to copy/paste code into terminal?) into my terminal (I know how to start terminal, but my students will not know). And when there’s an error, like
“Error: failed to create symlink /Users/kevin/.juliaup/bin/julia. Caused by: File exists (os error 17)”
there is no recourse. No help. I have 30 students in a course that uses Julia — they will each get their own error message and expect me to help.

  1. Why has the install process gotten so much worse?
  2. How do I complete my install, in light of the above error?
1 Like

1 Like

Here you use juliaup see this
(Symlink error when link/file exist · Issue #773 · JuliaLang/juliaup · GitHub)

You can skip this down on the same page and download the binary like (.dmg) for your OS

3 Likes

How’d I miss that? Thank you mohamed.d180!

2 Likes

The issue with symlink existing was created on 21 dec 2023.
Today is 8 Aug 2024.
Why is this issue not fixed even today?
Should not the juliaup installation process first check if this issue exists AND if it does exists print out a newbie friendly text that

  1. Explaining what the issue is
  2. Propose a newbie friendly instruction on how to fix it

This is NOT Rocket Science.

If an old installation infrastructure exists, then offer the user a process to remove the old infrastructure. Then ask the user to install again after the removal of the old infrastructure.

Just me venting…

2 Likes

Well instead of venting you could also just go ahead and do it. It’s all open source after all.

I agree it’s not rocket science but a few things need some thought because there are details that matter. So by all means if you want this fixed just do it. If can’t/don’t have time/etc then also fine. But please keep your pointless negativity at bay.

5 Likes

This negativity is not pointless. First, it draws additional attention to a rather important issue. Second, @StevenSiew suggests what can be done about it. The common FOSS sentiment “do it yourself or shut up” is not always helpful.

3 Likes

I totally agree that this is an important issue and probably should be fixed soon. However I really dislike the tone of @StevenSiew. On top the comment does not provide much beyond “well we should check better, provide better explanations and a better way forward” which at that level is easy to say and not very constructive/actionable.
I am totally one for constructive criticism, but that can be done in a more neutral/respectful manner.

Perhaps the post isn’t supposed to come off as condescending as it reads to me. Tone is kinda ambiguous in written text after all. I am totally prepared to accept that this is a misunderstanding. However it does close with

Which for me transports that the author indeed wanted to load off their annoyance. Which I feel is “pointless negativity” in the context of a civil discussion.

I also agree fully with you on that point. But still think it’s an appropriate response to comments that are mainly just venting off frustration.

2 Likes

With respect to all responses above, but we must say that removing the previous installations of julia is the user responsibility (E.g the path var which may affect the use) , And that mentioned in installation.

Although adding issue to juliaup if any one has good solution.
(guideline to remove previous julia installations completely · Issue #1007 · JuliaLang/juliaup · GitHub)

1 Like