-
-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Actually publish to brew #297
Comments
afaik, all you need is a git repo and a build command for homebrew, ex: https://github.com/Homebrew/homebrew-core/blob/master/Formula/n/nebula.rb a formula is an instance of the Formulae class in ruby, which has a lot of default behavior, so it should be simple. there's also automatic bots that will use https://docs.brew.sh/Brew-Livecheck to check for new versions, so it should be low-maintenance as long as the build api doesn't change |
better rust example: https://github.com/Homebrew/homebrew-core/blob/master/Formula/r/ripgrep.rb |
the guide for what brew lints are wanted for a new formula: https://docs.brew.sh/How-To-Open-a-Homebrew-Pull-Request |
fwiw, we already generate a formula: https://github.com/orogene/orogene/releases/tag/v0.3.31 so I guess this is just figuring out how to best create those PRs against brew and ideally automate the process. |
hmm ig the advantage of automatically generating PRs from here is that they're closer to synchronous w/ release rather than relying on the homebrew git bot to generate a PR? |
Following up on ^^: there's basically two options/paths: you stick your homebrew formula that you're generating into a tap or you go through their new formula process and their bot will then monitor this repo and update their accepted formula (and all the binary artifacts that they will generate) automatically. But the formula you're generating will probably not be accepted by them as-is and if you use tags & releases, then you generally don't have to notify them that your repo has been updated unless you want ASAP updates on the formula they carry. |
Put up Homebrew/homebrew-core#147422 as a draft PR of option #2 - it definitely needs some work though :p |
Linking cargo-dist's docs on doing this here: https://opensource.axo.dev/cargo-dist/book/installers/homebrew.html |
we're generating brew-related artifacts now with the latest version of
cargo-dist
, but we're not actually uploading it to brew. Should probably figure out how to do that. If anyone wants to pick this up, I'd appreciate the help, especially if we can automate it :)The text was updated successfully, but these errors were encountered: