toolroom.observe¶
Install one release, read what it accepts, and throw it away.
The unit of the gather, pure in (tool, version): requests for the same release dedupe on the futures work key, and arrival order is nobody's business: the record places each version at its own position whatever order these finish in.
A real task deliberately, not a helper. The task boundary is what buys
each observation its own environment: a body call copies the caller's
overlay, so the PATH written around extraction here is this
observation's alone, while the sandbox variables and prefix PATH the
caller set flow in — and on into every subprocess the tiers spawn.
None — a release that would not install, or a binary that would not
describe itself — is a hole for the caller to report, never an error:
the chain stays contiguous by construction, and a later run fills it.
Hidden: this task is not listed by fm --list, --tree or completion — it runs like any other when named.
fm toolroom.observe <tool> <version> [--tag=VALUE] [--date=VALUE] [--published=VALUE] [--requires-python=VALUE] [--scratch=VALUE]
| Parameter | Type | Default | Description |
|---|---|---|---|
<tool> |
required | ||
<version> |
required | ||
--tag=VALUE |
"" |
||
--date=VALUE |
"" |
||
--published=VALUE |
"" |
||
--requires-python=VALUE |
"" |
||
--scratch=VALUE |
"" |
Returns: an object (or null)