Keep in mind that the overlay packages section may show packages that were removed in favor of the synced package. In your list, glmark2
was just imported from the AUR to the Arch community repo so we dropped our overlay. chromium
and libreoffice-fresh
packages were fast-tracked previously.
How often do you check for orphan and foreign packages?
- After every update automated (hook or script)
- After every update manually
- Once a month
- Once a year
- When I think about it
- Never
0 voters
When you come across orphan packages, what do you do?
- Leave them alone
- Just remove them
- Remove after doing some research
- Mark them --asexplicit, so they donât appear in the list
- Donât know enough to take action
0 voters
When you come across foreign packages, what do you do?
- Update IgnorePkg in /etc/pacman.conf and use as-is until it dies
- Look for alternative software in Manjaroâs repositories to fill the need
- Use the AUR version of the package
- If in the AUR, vote, and hope the package is promoted
- Donât need the software anyway, so remove it
- Need something to fill the void, but removed it
0 voters
Iâm not 100% confident on the whole overlay business, but Iâm getting there
Where would I report a feature request for the âpackage changesâ report that appears in the announcements?
Content moved to: Feature request for the "package changes" report that appears in the announcements
At this time, I sort of think of orphans, foreign packages and software removed as one project after an update.
With the lastest Stable Update, âKnown issues and solutionsâ, âSwitch to the base-devel meta package requires manual interventionâ (pacman -S base-devel
) reduced orphans from 15 to 7. Which makes sense given a number of the packages were the result of a limited, but needed, AUR packages.
Executing pacman -S -g 'base-devel' | wc -l
resulted in a change of 27 to 18
Typically I use the one-liner as outlined in the Arch Wiki as root:
pacman -Qtdq | pacman -Rns -
and yes, there are many orphans usually of the development packages used by AUR packages. But I donât mind cleaning them up, because if I need another AUR package, they get reinstalled as dependecies.
The only thing I am not sure sure about are flatpaks and how to prune them. Is it even necessary?
Iâll cleanup flatpaks from time to time using the following:
flatpak uninstall --unused
This only uninstalls runtimes that have been left over from removed apps and are no longer being used by others. You shouldnât need to do this as an update should clean it up, But it has come in handy.
In case you guys want some inspiration or just a tool to automate maintenance, this script should cover most use cases.