Open hzeller opened 3 years ago
Paging @speedy-beaver who might be able to give an overview of required steps to get there.
We do releases essentially on every commit, so to not annoy upstream brew with multiple pull requests a day, we should probably have our own brew repository that people can point their brew install to.
So looks like this might be possible just with github means https://brew.sh/2020/11/18/homebrew-tap-with-bottles-uploaded-to-github-releases/
I assume you would like the steps for the end user to be as follows:
brew tap google/verible
brew install verible
In that case, the homebrew formula should be a in github repo called homebrew-verible
under the google
org on github.
The idea would be that commits to the verible repo, would trigger version bump PR in the homebrew-verible repo, which in turn would trigger a bottle rebuild.
@hzeller - If this is the direction you want to go poke me and I'll get the google/homebrew-verible
github repository created for you.
Yes, Let's make a google/homebrew-verible
repo!
I started the process to get that created. Will ping you when it exists.
https://github.com/google/homebrew-verible now exists and @hzeller has admin control over it.
Yes, ready to accept pull requests there.
First PR with homebrew github workflows mentioned in doc referenced above:
Homebrew package is done here. To automatically update, work continues in #1904
Similar how we generate a new downloadable binary release with each merge, we should provide something similar for brew, the common package manager on MacOS.
We could probably use github packages to provide a brew bottle/tap of sorts ? Details need to be figured out.