Expand description
One overview of pending updates across the tools that keep this machine: the distribution’s package manager, an AUR helper, Flatpak and Nix. It reads what each tool already knows; an online check asks the network only through read-only commands. Updating is delegated to the tools themselves.
Structs§
- Channel
- One tool that updates part of the machine.
- Homes
- The directories that say how a copy was installed.
- Pending
- One package waiting for an update.
- Places
- Where to look, apart from the commands.
- This
Copy - The running HelixForge: its version, where it runs from, and so how it was installed.
Enums§
- Install
- How this copy of HelixForge was installed.
Constants§
- RELEASES
- Where HelixForge’s releases are.
Functions§
- apt
name/suite new arch [upgradable from: old]lines from apt list.- arrows
name old -> newlines: pacman -Qu, checkupdates, paru and yay -Qua.- columns
- Tab-separated
application versioncolumns from flatpak remote-ls. - date
- A UTC date, YYYY-MM-DD.
- dnf
name.arch version repositorylines from dnf list –upgrades.- install_
of - How the copy at
exewas installed;checkoutsays whether a directory is the root of a HelixForge checkout. - overview
- Every channel this machine has.
onlinealso asks the network, through read-only commands (checkupdates, the AUR helper, Flatpak’s remotes). - package_
asset - The release file a family’s package manager installs.
- plan
- A plan updating the channels in order, each through its own tool, one after another; a later channel waits for the native packages.
- zypper
v | repository | name | current | available | archrows from zypper.