Switch to Scoop for CLI tools on Windows #24

Open
opened 2024-04-07 20:10:51 +00:00 by benie · 0 comments
Owner

Currently using Chocolatey for all package management on Windows. While this is fine, when a package installs something which requires the PATH to be updated, its quite annoying to need to restart the terminal to be able to use it. Scoop has a cleaner way of handling this, where tools are exposed in a single directory on the PATH via shim scripts for the various invocation contexts.

This is the kind of change that should be all or nothing, since its also going to require uninstalling a bunch of Chocolately packages when they are replaced with Scoop packages.

Currently using Chocolatey for all package management on Windows. While this is fine, when a package installs something which requires the `PATH` to be updated, its quite annoying to need to restart the terminal to be able to use it. [Scoop](https://scoop.sh/) has a cleaner way of handling this, where tools are exposed in a single directory on the `PATH` via shim scripts for the various invocation contexts. This is the kind of change that should be all or nothing, since its also going to require uninstalling a bunch of Chocolately packages when they are replaced with Scoop packages.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: config/local#24
No description provided.