aboutsummaryrefslogtreecommitdiff
path: root/configs/maintenance-thresholds.toml
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-08 10:53:32 -0500
committerCraig Jennings <c@cjennings.net>2026-07-08 10:53:32 -0500
commita1d5e90af52ff4bf2cf5355a93f5d8073791464a (patch)
tree600a790969ca0a77d84203578b2a94df3f9335fc /configs/maintenance-thresholds.toml
parent602f5fa3ab5645dbe790373299718408ce0f8858 (diff)
downloadarchsetup-a1d5e90af52ff4bf2cf5355a93f5d8073791464a.tar.gz
archsetup-a1d5e90af52ff4bf2cf5355a93f5d8073791464a.zip
fix(install): mark pacman packages explicit after --needed install
pacman --needed skips a package that is already on the system as a dependency and leaves its install reason alone. A declared package can then sit as asdeps, surface as an orphan once its accidental dependent leaves, and get swept away by an orphan cleanup. expac and lm_sensors, both maintenance-console runtime deps, nearly went this way: they were asdeps on both hosts and only survived today's orphan sweep because something still depended on them. pacman_install now marks the package explicit after a successful install. The mark never runs on a failed install, and a mark failure never fails the install. I flipped expac and lm_sensors to explicit on ratio and velox by hand since the installer only runs on fresh systems.
Diffstat (limited to 'configs/maintenance-thresholds.toml')
0 files changed, 0 insertions, 0 deletions