@ai-ecoverse/slicc-bios 1.51.1 → 1.51.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -32,7 +32,7 @@ The other 20 tools are listed in [`src/packages/tools.json`](src/packages/tools.
|
|
|
32
32
|
- npm's `latest`, through the same listing rules as an optional package: provenance, exceptions, engines, and a walk-back of at most five versions;
|
|
33
33
|
- never older than the installed one;
|
|
34
34
|
- one that doesn't pass, or doesn't come back from pnpm, leaves the version it had. Its row reads *Not offered: …*.
|
|
35
|
-
- **While the first round runs:** a command of a tool that isn't there yet (`jq`, `curl`, `rg`, …) answers `jq: seven is still installing it; Install / Update shows its progress` and exits 127, in the terminal, for the agent and under sudo. Before the first round installs anything, seven writes one placeholder package, `slicc-pending-tools`, into `/opt/slicc/pending` (protected like the rest of `/opt/slicc`), with a `#!/bin/sh` script for each command those tools' npm docs list. The kernel scans that root last, after `/opt/slicc/tools` and `/opt/user`, so anything real wins as soon as it's installed. When the round ends, seven removes the whole root, whatever installed, so `command -v jq` and bash's own `command not found` tell the truth again. Later rounds put no placeholders.
|
|
35
|
+
- **While the first round runs:** a command of a tool that isn't there yet (`jq`, `curl`, `rg`, …) answers `jq: seven is still installing it; Install / Update shows its progress` and exits 127, in the terminal, for the agent and under sudo. Before the first round installs anything, seven writes one placeholder package, `slicc-pending-tools`, into `/opt/slicc/pending` (protected like the rest of `/opt/slicc`), with a `#!/bin/sh` script for each command those tools' npm docs list. The kernel scans that root last, after `/opt/slicc/tools` and `/opt/user`, so anything real wins as soon as it's installed. The round installs the essentials first, then the rest. When the essentials' batch ends, seven drops their placeholders and keeps only those of the tools still to come, so a first-batch tool that failed or was refused is plainly not found while the rest install, as its row says. When the round ends, seven removes the whole root, whatever installed, so `command -v jq` and bash's own `command not found` tell the truth again. Later rounds put no placeholders.
|
|
36
36
|
- **Offline:** what's installed stays. Nothing is fetched until npm answers again.
|
|
37
37
|
- **Moving an old profile over:** an existing profile has the tools in `/node_modules`. The installer keeps each one there until `/opt/slicc/tools` has it. When the installer can't read `tools.json` (a network error, a 5xx or broken JSON), it prunes nothing that run, since it can't tell a tool waiting to move from a dropped package; a deployment without `tools.json` (404) prunes as before. Then seven removes the old copy through the kernel, and its receipt and ledger entry through the installer (`retire`). A tool therefore never disappears, offline or not.
|
|
38
38
|
- **Install / Update:** each tool has a row (`tools:<id>`, `preinstalled: true`), with the version it has, what npm offers, and why a newer one isn't offered. Retry or Update checks again. There's no Remove.
|