Ideally, when I do an update, two things I look for afterwards:
I can’t remove all orphans, well I could, they’d just be reinstalled . Plus I do want to know why things are happening. I have a list of packages that were installed, I believe, mostly because of the AUR packages: autoconf, bison, debugedit, flex, guile, make, patch, pkgconf, squashfs-tools. Most are in “Group=base-devel”.
The last install orphaned 3 more packages (see below). Talked to a colleague and they are of the stance, so what no one is using them, but I’m more of, keep the system “clean” to more readily spot potential problems and prevent problems. I’m think’n it might be easier to stay on top of it when the list is small.
It does take some time to determine why something was installed in the first place and why it isn’t needed any longer. I have a VM created with the same ISO as my host machine. That helps with why it was installed. Then a Internet search helps with why it isn’t needed any longer.
---------------------- show_pacman_orphans ----------------------
===> pamac list -o
lib32-faudio 23.01-1 multilib 285.8 kB
lib32-lcms2 2.14-1 multilib 437.4 kB
libvisual 0.4.0-8 extra 499.5 kB
I am particularly watchful of the packages that have been removed from Manjaro’s repos and are in AUR. It is actually worse, at the moment, if they are in the AUR, because pamac will gladly update ALL of them. I use pacman, but pamac for AUR packages in an automation script.
The last update (jan+feb) added two more packages. I’m up to 12 foreign packages. I started out with 3 that I explicitly installed from the AUR.
Manjaro package change document
I wish I could make heads or tails out of the Manjaro package changes document in the Announcement.
Example: Package changes ( Thu Feb 2 01:37:47 CET 2023 ).
A lot of the document makes sense. The majority of the document contains package name, the current version and updated version, like 0ad.
Where it gets messy is with the “-” in the current and updated version columns, and the base package name still exists.
In the first snippet below, only bsdiff is no longer in the Manjaro repos. So if I want to know, which packages are no longer in the Manjaro repos, it isn’t enough to look for a “-” in the last column, the user has to search the document for the package name to see if it appears some place else.
It’s nice to know what has been added (“-” in first column), but it is more important to know what has been removed and may will negatively impact a user. For example, to know quiterss was removed, a user had to page through a 4062 line document, and on line 2019 there it was
I have a script now where I only grab the line with a dash in the last column so I can quickly spot removals, but it needs to be refined because a dash in the last column doesn’t necessarily the base package was removed.
0ad a26-3 a26-4
glmark2 2021.12-1 -
bsdiff 4.3-12 -
glmark2 2021.12-1 2023.01-1
chromium 109.0.5414.119-1 -
libreoffice-fresh-af 7.4.5-1 -
chromium 109.0.5414.74-1 109.0.5414.119-1
libreoffice-fresh-af 7.4.4-1 7.4.5-1
dbus-x11 1.14.4-1 -
ceph 15.2.17-1 -
qpdfview 0.4.18-2 -
quiterss 0.19.4-2 -