Packagers (Homebrew, .deb, .rpm) expect a man page, and we ship none.
What to do
Generate attempt.1 from the existing clap definition with clap_mangen, rather than hand-writing roff.
- A
build.rs in crates/attempt or a hidden attempt man --out <dir> subcommand — either is fine, argue for one in the PR. A hidden subcommand keeps the build simple and lets docs/releasing.md call it.
- Include the generated page in the release archive alongside the binary (
.github/workflows/release.yml, the Package step), and install it from the Homebrew formula (man1.install "attempt.1").
Done when
man ./attempt.1 renders with the subcommand list, and a release archive contains it.
Good first issue: mechanical, but touches the release workflow — ask if anything there is unclear.
Packagers (Homebrew,
.deb,.rpm) expect a man page, and we ship none.What to do
Generate
attempt.1from the existing clap definition withclap_mangen, rather than hand-writing roff.build.rsincrates/attemptor a hiddenattempt man --out <dir>subcommand — either is fine, argue for one in the PR. A hidden subcommand keeps the build simple and letsdocs/releasing.mdcall it..github/workflows/release.yml, thePackagestep), and install it from the Homebrew formula (man1.install "attempt.1").Done when
man ./attempt.1renders with the subcommand list, and a release archive contains it.Good first issue: mechanical, but touches the release workflow — ask if anything there is unclear.