docs: Include scoop method of installation in README

[akielbowicz]

Hi,
A few days ago in juliaup can be installed using scoop. It was enabled with ScoopInstaller/Main#6210

Personally I been using scoop for a few years already on my personal and my work Windows machines and never had any issue. I prefer scoop over winget for cli tools as it eases the way to manage it and find issues.

Hopefully this helps with #343

[davidanthoff]

Couple of thoughts:

• Is there a plan to update the version that is available via scoop when we release new builds? For other platforms we automatically update things as part of the Juliaup release process (https://github.com/JuliaLang/juliaup/blob/main/.github/workflows/release.yml), we should probably do the same for scoop, right?
• If we actually have a package manager use the portable builds, we should probably upload them to S3 and then download from there, rather than from GitHub directly, but also see below about other options.
• Could this be listed as julia rather than juliaup in the scoop repo? So that the install command is scoop install main/julia. That is what we already have for winget, and given that Juliaup now is the official installer for Julia, I think that would make things much clearer.
• Does scoop support MSI or MSIX installers? If so, maybe we should use those instead? They handle more things properly, like modifying PATH, adding start menu items, potentially down the road package identity etc. And they exist and are available at the various official download pages.
• I'm happy to mention the scoop option here, but we should not make it the next best option if the Windows Store doesn't work. At the end of the day, the "official" story should be: 1) Windows Store, 2) App installer, 3) MSI, 4) all the other third-party options (which include scoop).

[akielbowicz]

Hi @davidanthoff, thanks for your thoughts

Is there a plan to update the version that is available via scoop when we release new builds? For other platforms we automatically update things as part of the Juliaup release process (main/.github/workflows/release.yml), we should probably do the same for scoop, right?
If we actually have a package manager use the portable builds, we should probably upload them to S3 and then download from there, rather than from GitHub directly, but also see below about other options.

Scoop does update the packages versions manifest automatically through some scheduled process. The new version information can be obtained through different mechanisms, see App Manifest Autoupdate. Currently for Juliaup is configured to get the information from the GitHub Releases, as you can see in the manifest commit history that last week the manifest it was updated to the version 1.17.9.

Related to the autoupdate I decided to download from the GitHub Release directly because they were the only ones that had the version on the name, the links detailed on the README do not have the version information, (ie "https://install.julialang.org/Julia-x64.msi"). I suppose that this could be fixed by changing the Rename Step to copy the files instead of renaming it, in favor of not breaking anything that depends on the names as they are now.

Could this be listed as julia rather than juliaup in the scoop repo? So that the install command is scoop install main/julia. That is what we already have for winget, and given that Juliaup now is the official installer for Julia, I think that would make things much clearer.

I will say that it's possible but it might bring some issues, there has been a julia manifest since 2014 and I suspect that changing it will break other scoop users setups.

Does scoop support MSI or MSIX installers? If so, maybe we should use those instead? They handle more things properly, like modifying PATH, adding start menu items, potentially down the road package identity etc. And they exist and are available at the various official download pages.

Yes, the MSI installer seems to work without any issues. For example, the rust manifest uses it. As mentioned above, the MSI files must be published with the version in their name.

I'm happy to mention the scoop option here, but we should not make it the next best option if the Windows Store doesn't work. At the end of the day, the "official" story should be: 1) Windows Store, 2) App installer, 3) MSI, 4) all the other third-party options (which include scoop).

Of course, I updated the PR to mention the Scoop installation under the Software Repositories section