You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4062d69
Browse filesBrowse the repository at this point in the historyBrowse files
Ship the tool as a .deb, an .rpm and a pacman package
A tarball has to be upgraded by hand and nothing on the machine knows it is
there. Every release now also carries three package formats for both
architectures, so the tool is installed and upgraded the way everything else
on the system is.
The nfpms block puts the binary in /usr/bin, because the package manager owns
it, and README, LICENSE and the example config under /usr/share/doc. It
provides the command name and conflicts with anything else shipping it, so a
second copy is a conflict rather than a silent overwrite.
GoReleaser cannot read tool.json, so the package description is a copy of the
tagline. `make manifest` now also runs the kit's check-nfpm.py, which fails
when the two disagree, and CI runs it on every push.
`install.repo_url` points at the family package repository, which is what the
README's one-time setup is derived from: the one-liner, and next to it the
commands it stands for. The release job tells tui-tools/pkgs that new
packages exist, so the repository rebuilds on release rather than on its
weekly run; the step is inert until PKGS_DISPATCH_TOKEN is set.
0 commit comments