majordomus distribution
How this project is packaged, published and installed: the platforms, the artifact names, the installer, the releases
majordomus distribution
Usage
majordomus distribution [OPTIONS] [COMMAND]Commands
- majordomus distribution show The model: the install command, where an installation goes, and every declared target
- majordomus distribution status Whether the advertised one-line installation works right now, and what is missing when it does not
- majordomus distribution validate Every invariant of the model and of the release records; exit 10 with each violation named
- majordomus distribution targets Every declared target, one line each, with the artifact name it derives
- majordomus distribution matrix The release build matrix, as the release workflow reads it
- majordomus distribution artifact The archive name and root directory a target and a tag derive
- majordomus distribution releases Every recorded release, newest first, and the one an unpinned installation resolves to
- majordomus distribution metadata The public metadata one release record publishes, rendered from the record alone
- majordomus distribution build What this executable is: version, target triple, profile, commit
Arguments
| argument | value | default | description |
|---|---|---|---|
| --repo | <PATH> | — | Start the search for the repository root here (default: the current directory) (accepted by every subcommand) |
| --discovery | vcs | filesystem | vcs | How declarative files are enumerated (accepted by every subcommand)
|
| --strict | flag | — | Refuse to proceed when any file of the layer carries an error diagnostic (accepted by every subcommand) |
| --share | <DIR> | — | The tool distribution's share directory (kinds.yaml, schemas/); default: $MAJORDOMUS_SHARE, then the repository's own share/, then the one beside the executable (accepted by every subcommand) |
| --format | text | json | text | Output shape (accepted by every subcommand)
|
Examples
-
How this project is installed
`distribution` with nothing after it shows the model: the one-line install command, where an installation goes, and how many platforms a release builds. Every value comes from share/distribution.yaml, which is the only place any of them is written.
$ majordomus distributionVerified by the example tests: exits 0; prints binary, install, targets.
Where this comes from
Declared once in apps/majordomus-cli/src/cli.rs: clap for the structure, typed Rust metadata beside it for the examples. This page, majordomus distribution --help, docs/generated/cli.md and docs/generated/cli.json are projections of that one declaration.
The whole command line on one page: the registry's command-line page. The task lifecycle (init, start, finish, doctor, ...) belongs to the shell tool, a different program: Commands and its specification.