[Feature]: scoop support (a popular Windows package manager)

[God-damnit-all]

Scoop is a command-line installer for Windows.

1. Why Do You NEED This Feature?

I NEED this feature because:

• I'm lazy.

2. What Is NOT Possible Right Now?

Currently I cannot:

• Have a package manager automatically keep forge up-to-date for me.

3. What WILL Be Possible With This Feature?

With this feature I will be able to:

• Have forge be automatically updated when using scoop update * or scoop update forge.

Proposed Solution (User Experience)

If not made available in the official main or extra bucket repositories, I would add the bucket repo you provide via scoop bucket add <name> <repo> which would be a json file that indicates what the latest version is as well as the download url for scoop to use. After running scoop update, that will make forge something that can be installed with scoop install forge.

Use Cases

1. Have forge be automatically updated when using scoop update * or scoop update forge.

Feature Category

Other

Priority/Impact

Low - Minor improvement

Examples from Other Tools

task-keeper didn't want to have to go through official channels to have their project added to scoop and instead just created their own repo for it:

https://github.com/Zevan770/scoop_zev/blob/main/bucket/task-keeper.json

Contribution

• I'm willing to submit a PR to implement this feature
  • This is going to be very dependent on your personal preferences for handling deployment, which is something developers tend to want to do in their own way. I also lack familiarity with the cargo-dist workflow.
• I can help with testing
• I can help with documentation

Additional Context

No response

✅ Pre-submission Checklist

• I have clearly explained WHY I need this feature (not just that it would be nice)
• I have described what is NOT currently possible in detail
• I have explained what WILL be possible with concrete examples
• I have provided specific use cases and workflows
• I have searched existing issues to avoid duplicates

[soerennielsen]

There are winget, chocolatey and scoop afaik for package management on windows.

winget is built in. Maybe that is the more natural choice?

[God-damnit-all]

There are winget, chocolatey and scoop afaik for package management on windows.

winget is built in. Maybe that is the more natural choice?

The problem with winget is there is no way to batch update apps you've installed through winget, you can either update one thing at a time or you update ALL apps on your computer. And it doesn't tell you what had been installed through winget, either.

Scoop stays in it lane.

[soerennielsen]

What?

I have never used Scoop, but I have used WinGet, Choco and a number of apt, qpkg, opkg, snap, etc. on various Linuxes.

It does the same thing.

Winget update will show you all packages with updates.
Winget update package1 package2 package3 will update exactly those and only those.
winget upgrade --all
Winget list - will show you the packages it installed

I get that we all have different preferences, but not picking the default package manager that everyone has is just ... strange. Choco and Scoop is likely also nice, but they are niche compared.

[God-damnit-all]

What?

I have never used Scoop, but I have used WinGet, Choco and a number of apt, qpkg, opkg, snap, etc. on various Linuxes.

It does the same thing.

Er, no, it doesn't.

When you're on Linux, you don't expect apt to upgrade packages you installed from snap.

With WinGet it's the same but even more ubiquitous: When I run winget list it lists things I've installed manually, without using a package manager of any sort. I manually did a CUDA 12.6 install just the other day, and today running the winget list command to look for a good example, it lists 13.1.

Were I to run winget upgrade --all, it would attempt to install CUDA 13.1, which would break a lot of my shit.

With scoop, it only ever upgrades things I've installed from scoop.

[God-damnit-all]

I should also point out that WinGet lacks the knowledge of what was installed through WinGet, so you'd have to use some sort of wrapper to keep track of that. It's very annoying.

Honestly I'm often frustrated with how many common sense things WinGet lacks. Hell, only just recently did we finally get a parameter to disable the progress "spinner" so stdout redirection isn't spammed with it. (It would've been nice to also make it so it outputs on stderr like Curl's progress meter does, but I'll take what I can get from it at this point.)

[github-actions]

Action required: Issue inactive for 30 days.
Status update or closure in 7 days.

[God-damnit-all]

.

[rnett]

@God-damnit-all I generally agree about scoop being better than WinGet, for it's better path management if nothing else. But for updating, check out UniGetUi. It has been a lifesaver for me.

[God-damnit-all]

@God-damnit-all I generally agree about scoop being better than WinGet, for it's better path management if nothing else. But for updating, check out UniGetUi. It has been a lifesaver for me.

I mean, UniGetUI is just a wrapper for all the package managers currently available for windows.

But I don't know, using a GUI app to manage CLI apps just feels wrong.