Proposal: maintain an official Homebrew tap
Could PI-Desktop maintain an official Homebrew tap for macOS releases?
I prepared a working tap repository here:
https://github.com/Fletcher-Alderton/homebrew-pi-desktop
It includes:
Casks/pi.rb for the official ARM64 and Intel macOS DMGs.- SHA-256 verification for both architectures.
- GitHub release livecheck support.
- A scheduled GitHub Action that detects the latest stable PI-Desktop release, recalculates checksums, updates the cask, and commits the change.
- Installation and upgrade documentation.
The current tap can be tested with:
brew tap Fletcher-Alderton/pi-desktop
brew install --cask pi
brew upgrade --cask pi
The cask downloads releases directly from vastsa/PI-Desktop; it does not duplicate or fork the application source. For official ownership, the tap could be transferred to the vastsa account or recreated as:
vastsa/homebrew-pi-desktop
Then the README and release documentation could point users to:
brew tap vastsa/pi-desktop
brew install --cask pi
The Homebrew core-cask submission passed its automated checks but was declined for inclusion, with maintainers suggesting an official third-party tap instead.
Proposal: maintain an official Homebrew tap
Could PI-Desktop maintain an official Homebrew tap for macOS releases?
I prepared a working tap repository here:
https://github.com/Fletcher-Alderton/homebrew-pi-desktop
It includes:
Casks/pi.rbfor the official ARM64 and Intel macOS DMGs.The current tap can be tested with:
The cask downloads releases directly from
vastsa/PI-Desktop; it does not duplicate or fork the application source. For official ownership, the tap could be transferred to thevastsaaccount or recreated as:Then the README and release documentation could point users to:
The Homebrew core-cask submission passed its automated checks but was declined for inclusion, with maintainers suggesting an official third-party tap instead.