Workstation basics: fonts, docker-compose, snapd, flatpak, cups, bluetooth, xclip, dmenu (hq to-be 42 phase 2), tools in Go #269

2026-10-04T11:02:37Z

mesh-admin commented

2026-10-04 11:02:37 +00:00

fonts: JetBrains Mono Nerd Font, Inter, Nerd Fonts Symbols and Noto Color Emoji. One account fontconfig file binds monospace, sans and emoji, so every program agrees.
docker-compose: projects found from labels; config redacts secrets; down never removes volumes; long acts run as jobs.
snapd: tools only. The package is AUR, so the module waits for research 027 Q1 (P2).
flatpak: list, runtimes, unused (computed without changing anything), update and remove.
cups: both Brother queues print driverless, so no vendor driver is declared.
bluetooth: bluez declared; pair, connect and battery.
xclip: copy and paste in the operator's X session, found from the window manager's environment.
dmenu: the package (fixes dunst's broken dmenu line) and a menu tool.

Tests pass in all eight; module check passes all 90 manifests.

- **fonts:** JetBrains Mono Nerd Font, Inter, Nerd Fonts Symbols and Noto Color Emoji. One account fontconfig file binds monospace, sans and emoji, so every program agrees. - **docker-compose:** projects found from labels; `config` redacts secrets; `down` never removes volumes; long acts run as jobs. - **snapd:** tools only. The package is AUR, so the module waits for research 027 Q1 (P2). - **flatpak:** list, runtimes, unused (computed without changing anything), update and remove. - **cups:** both Brother queues print driverless, so no vendor driver is declared. - **bluetooth:** bluez declared; pair, connect and battery. - **xclip:** copy and paste in the operator's X session, found from the window manager's environment. - **dmenu:** the package (fixes dunst's broken `dmenu` line) and a menu tool. Tests pass in all eight; module check passes all 90 manifests.

mesh-admin added 8 commits 2026-10-04 11:02:37 +00:00

fonts: the five decided faces as packages, and what the generic families mean (hq to-be 42 phase 2.1) 86cf6d438d

JetBrains Mono Nerd Font for monospace, Inter for the interface, the Nerd
Fonts symbols and Noto Color Emoji as fallbacks, Noto for serif. One owned
fontconfig file in the account's conf.d maps monospace, sans-serif,
system-ui, serif and emoji, bound `same`: measured with fontconfig 2.18, a
weakly bound preference loses to Noto Sans Mono. Families today's configs
name but the laptop lacks (Iosevka, the old JetBrains name) stop falling
back to sans-serif.

Six Go tools: families, match, glyph, sources (which hand-copied files can
go and why), config, cache-rebuild. The README lists the hand-copied files
to remove and the modules that must name the new family.

docker-compose: the package, and its projects as tools (hq to-be 42 phase 2.9) 45befbbd02

Compose and nothing else, for the two workstations, where it is already
installed by hand; the runtime, buildx and the group stay the docker
module's. Nine Go tools: projects (with their directories from the
containers' labels), ps, logs, a rendered config with secret-looking values
redacted, and up, down, restart and pull by directory or name. Acts run as
jobs inside the bundle, waited on for 18 s and followed with
docker_compose_job, because an up that pulls outlasts a call. down never
removes volumes.

snapd: tools for the snaps, the package blocked on the mesh's AUR repository (hq to-be 42 phase 2.9) db297e8bdd

snapd is not in the official repositories, and ADR 0205's archive does not
fit a daemon with setuid helpers, so the module declares nothing until
research 027 question 1 (P2) builds it into the mesh's own repository. Not
even its units: on the laptop they do not exist, and the module would fail
there.

Ten Go tools that work wherever snapd is installed and say so where it is
not: status (with AppArmor's absence from the kernel named), list, info,
updates, disk usage with the disabled revisions' share, services, changes,
and install, remove and refresh through sudo -n with --no-wait, answering
snapd's change id.

flatpak: the package, Flathub with it, and the installations as tools (hq to-be 42 phase 2.9) 152ef9621d

The package ships Flathub in /usr/share/flatpak/remotes.d, so the module
declares no remote of its own and checks it instead. Eleven Go tools: list,
runtimes, remotes (naming the desktop's duplicate user Flathub), updates,
unused, disk usage, and install, remove, update and remove-unused, the
system installation's acts through sudo -n and the account's without.

uninstall --unused has no dry run, so flatpak_unused works it out from
flatpak's own answers: an application's runtime and SDK, the extension
points of what is used, and pins. Acts run as jobs inside the bundle,
because an install outlasts a call.

cups: the scheduler and driverless printing, and the printers as tools (hq to-be 42 phase 2.9) b352f3920e

Research 027 asked for cups with the printer's driver. Measured: both
Brother queues already print through IPP Everywhere, so cups and
cups-filters are the whole driver, and the AUR vendor packages beside them
serve no queue. The desktop's Canon is the exception: its 2012 driver is
AUR-only and waits for the mesh's package repository; it stays as found.

Seven Go tools: printers (state, device, driverless or not, supply levels),
queue, cancel (the account first, sudo -n when CUPS refuses it), print,
default, resume, and drivers (which packages bring drivers, which are
foreign, which no queue uses).

bluetooth: the stack, its daemon, and the devices as tools (hq to-be 42 phase 2.9) 3b43a1ef4d

bluez and bluez-utils, and bluetooth.service running and enabled. On both
workstations bluez is installed only as a dependency; declaring it keeps a
clean-up from taking it.

Nine Go tools over bluetoothctl: controller, power, devices with battery
where reported, a bounded scan, connect, disconnect, trust, pair (an agent
that confirms nothing, for headphones) and remove. An act whose output says
it failed is an error whatever the exit status, and one bluez refuses the
account is repeated through sudo -n.

xclip: the package, and the operator's clipboard from the mesh (hq to-be 42 phase 2.7) b1b7e58e4b

A package and nothing else, the tool the desktop's scripts depend on.
Four Go tools: copy, paste (text, base64 for other types, empty when
nothing), targets and session.

The runtime is given no session words, but runs as the account in the
machine's own namespace, so the session is found rather than configured:
the process's DISPLAY, else the account's processes' DISPLAY and XAUTHORITY
from /proc (the window manager's first), else the only X socket with
~/.Xauthority. Measured with both variables unset: :1 found through i3, the
server answered. With no session every tool says so and runs nothing.

dmenu: the package, which makes the notifier's menu work, and a menu tool (hq to-be 42 phase 2.7) 838a6e510b

Research 026/04 counted two plain dmenu calls failing with dmenu installed
nowhere. Measured, they are one line on each workstation: dunst's
`dmenu = /usr/bin/dmenu -p dunst:`. Installing the package fixes both by
existing; the line stays the dunst module's.

No claim: node-launcher is not in the controller's seat table yet, and the
module says so. Two Go tools: menu, shaped like that seat's verb (chosen
line, index, typed, cancelled, timed out within 25 s), and session.

mesh-admin merged commit b8982b4a7c into main

2026-10-04 11:02:42 +00:00

mesh-admin deleted branch feat/phase-2-workstation-basics-rebased

2026-10-04 11:02:43 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#269