Skip to content

toolroom.prime

Read past releases into the option history, deepening each chain.

Reaches below each tool's floor, up to --count releases further back. Nothing already written is touched, and a release the chain already has is skipped — so a prime interrupted by a rate limit is resumed by running it again.

The releases are gathered in parallel, a bounded wave at a time — installing a release and reading its --help depends on no other release, and the chain assembles whatever order the observations arrive in. A release that will not install, or whose binary will not describe itself, is a hole: named in the report, filled by a later run, and never the end of the tool's walk.

--prefix points at a fm toolroom.provision directory, and the tiers are driven from its binaries. That is not the same nicety it is on sync: uv carries CPython's download index inside itself, so a stale uv reports a stale newest python and the walk silently starts too low.

fm toolroom.prime [--only=VALUE] [--count=INT] [--keep] [--prefix=VALUE]
Parameter Type Default Description
--only=VALUE "" prime just this tool
--count=INT int 20 how many releases back to read
--keep flag false leave the throwaway environments behind
--prefix=VALUE "" drive the tiers from this prefix's bin/

Example

$ fm toolroom.prime --keep