toolroom.sync¶
Match this machine to toolroom.lock, writing the lock first if it must.
What sync does for the tools alone, in uv's shape. By default the
lock is written when there is none or when the sites' requirements
have moved past it, and then every tool it names is supplied
through the store, a receipt per tool says what reached PATH, and
the stubs follow. A tool the store cannot supply is reported and
the others are supplied.
--frozen installs the lock exactly as it is and resolves
nothing, which is what a CI job wants: a runner's checkout is
judged, never re-resolved. --locked refuses when the lock is
not current instead of writing it, which is the assertion a gate
makes. --offline reads the catalogue and the deployments from
the machine's store alone.
| Parameter | Type | Default | Description |
|---|---|---|---|
--frozen |
flag | false |
install the lock as it is; never resolve |
--locked |
flag | false |
refuse if the lock is not current |
--offline |
flag | false |
supply from the machine's store and its sources only |