i3status-rust, docker-compose: each module declares the packages it needs (issue 628)

i3status-rust left pacman-contrib to the pacman module because two modules declaring one package was once refused; ADR 0303 allows it, so the bar declares what its update block runs. docker-compose's README said the package goes with the module, which the node-engine never does.
2026-10-13 11:52:38 +00:00
parent 19ecad261c
commit e79197d5a1
3 changed files with 9 additions and 3 deletions
@@ -19,8 +19,9 @@ runtime is missing or unreachable rather than an empty list.

 - **An owner for a package both workstations already carry.** On both, `docker-compose` 5.5.0 is
  installed explicitly by hand, as the plugin in `/usr/lib/docker/cli-plugins`. Assigning the module
-  changes nothing on disk; from then on the package is the mesh's, upgraded with the machine and
-  given back when the module goes.
+  changes nothing on disk; from then on the mesh says the package is needed, and it is upgraded with
+  the machine. Unassigning the module leaves the package installed: the node-engine never removes a
+  package a declaration stopped naming (novox/hq ADR 0303).
 - **The projects become visible from the mesh** without a shell on the machine: which are running,
  where their files are, their containers, logs and rendered configuration.
 - **No account-level copy of the plugin** exists on either workstation (`~/.docker/cli-plugins` is