Chocolatey is a Package Manager for Windows applications that has been around for much longer (~9 years) than WinGet. For that reason and its extensive package catalog, it's widely used and often the preferred alternative over WinGet, especially within corporations.
The Swift community distributes toolchain packages through WinGet, but there is no official package for Chocolatey. Preparing a Chocolatey package for Windows shouldn't be hard. However, the community repository is unlikely to accept new package contributions. Perhaps they would if the package is backed by the Swift organization? In fact, the community repository is just a place to host package sources, but any publicly accessible repository would do. The quirk is that you need to register the package source with Chocolatey. You need an account, that the package would be associated with.
I'd be willing to set up the repository, the initial package(s) and keep it/them up to date (ideally automate it). But before I do, there are a few things I want to clarify with the community:
- Is there an interest and the willingness to support Chocolatey packages for Swift at all?
- Would
github.com/swiftlangbe the place to host the package source repository? - The Chocolatey account would ideally be associated with the Swift organization than an individual. How would that work? How would credentials be maintained and shared?
I'm looking forward to hearing what others think. Please mention people who might have a say on this since not everyone might be following the Windows category and this has overlap with Build and Packaging as well as swift.org Website topics. I'll start with @mishal_shah and @compnerd. 