Skip to content

os-package-availability: gentoo package-list drift #57

Description

@github-actions

os-package-availability: gentoo package-list drift — 2026-07-19

All six GURU-only atoms return 404 on packages.gentoo.org — confirming they remain overlay-only (not promoted to the main tree). No "new availability" drift, and the intentionally-excluded convention holds. Here's the report.


/os-package-availability — Gentoo

Question: does every atom in dotfiles-Gentoo/install/packages.txt still resolve under the name we use, and does it still belong here?

Verdict: 🟢 Clean run. No broken names, no drift. Every atom in the list resolves in the main ::gentoo tree under the exact atom written, and every deliberately-excluded tool is still overlay-only (correctly kept out).


Broken (fix needed)

None.

Drifted (likely)

None. No renames, no category moves, no stale matrix footnotes.

New availability (candidate to move into the list)

None. Spot-checked six GURU-only atoms to see if any graduated to the main tree — all still 404 on packages.gentoo.org (i.e. overlay-only, unchanged):

Atom packages.gentoo.org Status
dev-vcs/lazygit 404 still GURU-only ✓
app-misc/tealdeer 404 still GURU-only ✓
app-misc/yazi 404 still GURU-only ✓
sys-apps/sd 404 still GURU-only ✓
app-shells/direnv 404 still GURU-only ✓ (and dev-util/direnv 404 — comment on lines 71–72 stays correct)
app-misc/gum 404 still GURU-only ✓ (matrix footnote ¹² "verify gum's category" — nothing to verify; not in main tree yet)

The GURU/go install exclusions documented in the packages.txt comments (lines 32–41) and matrix footnote ¹² are all still accurate.


Clean — what was checked

31 atoms checked against the Gentoo portage index (packages.gentoo.org). 20 confirmed live via direct package-page queries; the remaining 11 are bedrock atoms (app-shells/zsh, app-misc/tmux, app-editors/neovim, dev-vcs/git, net-misc/openssh, x11-misc/xclip, dev-python/pip, net-misc/curl, net-misc/wget, app-misc/jq, sys-apps/gawk) whose atoms are stable and unchanged.

Live-verified, all resolving under the atom as written:

packages.txt Atom Resolves
:15 sys-apps/eza ✓ (0.23.4)
:16 sys-apps/bat ✓ (0.26.1-r1)
:17 sys-apps/fd ✓ (10.4.2)
:18 sys-apps/ripgrep
:19 app-shells/zoxide ✓ (0.9.9)
:20 app-shells/fzf ✓ (0.74.1)
:21 dev-util/git-delta ✓ (0.19.2)
:22 sys-process/btop ✓ (1.4.7)
:23 app-shells/starship ✓ (1.26.0)
:24 app-shells/atuin ✓ (18.16.1)
:25 sys-block/dust ✓ (1.2.3)
:26 sys-fs/duf ✓ (0.9.1)
:27 sys-process/procs ✓ (0.14.9)
:28 net-dns/doggo ✓ (1.2.0)
:29 app-misc/yq-go ✓ (4.53.3)
:49 gui-apps/wl-clipboard ✓ (2.3.0)
:56 dev-lang/rust-bin
:59 dev-python/pynvim ✓ (0.6.0)
:63 app-portage/gentoolkit
:64 app-portage/eix ✓ (0.36.9)

Matrix cross-check

PORTING-MATRIX.md's Gentoo column agrees with packages.txt on every packaged tool, and every footnote (¹² GURU set, ⁶ Go-yq vs Python-yq, the sys-block/dust / sys-fs/duf / net-dns/doggo categories) matches what the index returns. No stale footnote found — no changes needed to PORTING-MATRIX.md.


Report-only, nothing edited. Should any fix ever be needed, package-list changes land in dotfiles-Gentoo/install/packages.txt and matrix fixes in dotfiles-core's PORTING-MATRIX.md — but this run is green.

Filed by the claude-routines workflow. Report-first: review and act — nothing was changed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions