axodotdev / axodotdev/cargo-dist
Feature Idea: Generate `homebrew` source packages?
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 149
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 32
Description
I had a user kindly package `river` for me, which is using `cargo-dist` for releases. I had intended to set up a tap to use the pre-built binaries, but before I did that someone submitted a source package.
In case this is another installer form y'all would be interested in generating, here is some context:
https://github.com/memorysafety/river/issues/31#issuecomment-2129596902
And here is the actual manifest they produced, which appears to use the signed github source release export:
https://github.com/Homebrew/homebrew-core/blob/2b59118b7ba6dbbe700400d12ead8ed8040a5ffd/Formula/r/river.rb
I don't need this particularly, it seems what the contributor submitted should auto-update based on GH releases? But I thought it was cool info to share, and a way to get cargo-dist packages with source into the main upstream homebrew cask.
Contributor guide
Research direction
Review the linked Homebrew manifest and the referenced River discussion first. Determine whether generating Homebrew source packages belongs in cargo-dist and what manifest or release behavior would define completion; the issue does not identify project files, tests, or a settled implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100