Skip to main content

Module matrix

Module matrix 

Source
Expand description

The manager × venue matrix for rk itself: which pairs land as a fragment, seeded where the manager file is absent, and which are a hand edit with a named reason.

The matrix guesses nothing it cannot read offline. release-kit’s crate name, flake output, and release archives are known, so the pairs that consume one of those render; the pairs that need a nixpkgs attribute, a source hash, or an asdf plugin nobody publishes are manual with that reason, and the report says so instead of inventing one. The dependency matrix in src/depend/matrix.rs has the same shape over an arbitrary source, and its reasons are about that source, so nothing is imported from it.

Structs§

Pair
One manager and one venue.

Enums§

Mode
How a pair lands in one target: the closed support vocabulary of the add report.
Support
Whether a pair renders, and why not where it does not.

Constants§

REASONS
Every manual reason the matrix can name, closed: a test holds each pair’s reason to this list.

Functions§

choose
The pair one add or sync serves, from the flags and the target.
default_venue
The first venue a manager renders a fragment for, or its first preference where every venue is manual.
preference
The venues a manager prefers, first first.
support
The support of one pair.