From 7c53c8113b53c3be157ba5df77b34a78d665c200 Mon Sep 17 00:00:00 2001 From: "Danilo M." Date: Fri, 25 Sep 2026 11:22:34 +0200 Subject: nvtable: SBo fallback lookup, label AppImage/flatpak installs Packages in none of my repos are looked up in the local SlackBuilds.org clone (NVTABLE_SBO overrides the path) and labelled [SBo]. SBo lagging upstream is not flagged repo-behind; upstream is still appended. With no SlackBuild anywhere, the label says how it is installed ([AppImage] or [flatpak]); [--] means neither. Co-Authored-By: Claude Opus 5.5 --- README.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 207cc8c..a61f5f1 100644 --- a/README.md +++ b/README.md @@ -21,10 +21,12 @@ the version shipped by the SlackBuild repo that packages it. Each row reads `[repo] package installed -> repo`, then the markers. The upstream version is appended only when the repo column does not already show -it: the repo is behind, or the package is not in any of my repos (`[SBo]`, -built straight from SlackBuilds.org). Repo labels: `personal` = -my-slackbuilds, `my-sbo` = sbo-slackbuilds, `pentesting` = -Slackware-Pentesting-Suite. +it. A package in none of my repos is looked up in a local SlackBuilds.org +clone (`[SBo]`, `NVTABLE_SBO` overrides its path); SBo lagging upstream is +not flagged 🟡, since that bump is not mine to make. With no SlackBuild +anywhere, the label says how it is installed (`[AppImage]`, `[flatpak]`); +`[--]` means neither. Repo labels: `personal` = my-slackbuilds, `my-sbo` = +sbo-slackbuilds, `pentesting` = Slackware-Pentesting-Suite. | marker | meaning | |--------|---------| -- cgit v1.2.3