3 ms·
The "app repository" is a github repository [1]. I'm not sure how I feel about that. It worked for appget, it's easy to audit, nobody can do any shenanigans wit
by wongarsu 5y ago
The "app repository" is a github repository [1]. I'm not sure how I feel about that. It worked for appget, it's easy to audit, nobody can do any shenanigans without obvious traces. But the UX could be better, for example this is what publishing a new version looks like [2]. I guess we can always build a separate UI.
1: https://github.com/microsoft/winget-pkgs https://github.com/microsoft/winget-pkgs
2: https://github.com/microsoft/winget-pkgs/pull/30035 https://github.com/microsoft/winget-pkgs/pull/30035
- erichurkman 5y agoFWIW this is how Homebrew, the most widely used package manager on macOS, does it. As an example, check out the 'formula' for installing Zoom: https://github.com/Homebrew/homebrew-cask/blob/master/Casks/zoom.rb https://github.com/Homebrew/homebrew-cask/blob/master/Casks/... I used to maintain a few packages and it was pretty dang easy to publish, test, vet, and distribute this way. Everything else is in Git, why not this, too?
- arrakeen 5y agothose PRs are appalling.. bots talking to each other, commenting to run bot commands, bots adding and immediately removing labels. as if the github PR user experience weren't bad enough