Man pagesΒΆ
Every mpm command carries a Unix manual page, walked out of the live command tree while this site builds. A manual therefore cannot describe a release other than the one it ships beside, which is the whole reason none of them is written by hand.
The index below is rendered by click_extra.sphinx from the click_extra_manpages list in docs/conf.py. Each entry points at the browser-viewable HTML rendering produced when mandoc (preferred) or groff is on PATH during the build.
mpm(1)β CLI options shared by all subcommands.mpm-cleanup(1)β Cleanup local data.mpm-config-template(1)β Print per-manager overrides as a TOML config template.mpm-doctor(1)β Diagnose managers health.mpm-dump(1)β Snapshot installed packages to a TOML manifest or a Brewfile.mpm-help(1)β Show help for a command.mpm-install(1)β Install a package.mpm-installed(1)β List installed packages.mpm-managers(1)β List the package managers detected on the system.mpm-orphans(1)β List orphaned packages.mpm-outdated(1)β List outdated packages.mpm-remove(1)β Remove a package.mpm-restore(1)β Install packages referenced in TOML files.mpm-sbom(1)β Export installed packages to a SBOM document.mpm-search(1)β Search packages.mpm-sync(1)β Sync local package info.mpm-upgrade(1)β Upgrade packages.mpm-which(1)β Locate CLIs on system.
The raw .1 files sit in this same directory, next to the renderings above, under mpm.1 for the root command and mpm-{subcommand}.1 for the rest. Reading them in a terminal covers the rest: reading one straight from the CLI with --man, installing the release bundle into MANPATH, and regenerating the set from source in a packaging build phase.