You are not logged in.
As my list of AUR packages increases, some of these I have only installed because some other package required it, but it is become harder to track why some of these packages were installed.
For example, I installed the package "skdet", which "rkhunter" can use to enable some tests but does not actually require it to be installed. The output of pacman for "skdet":
# pacman -Qi skdet
Name : skdet
Version : 1.0-1
Description : Simple rootkit detector that can be used by rkhunter.
Architecture : x86_64
URL : http://dvgevers.home.xs4all.nl/
Licenses : GPL
Groups : None
Provides : None
Depends On : None
Optional Deps : None
Required By : None
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 36.58 KiB
Packager : Unknown Packager
Build Date : Wed 18 Aug 2021 09:15:07 AM EDT
Install Date : Wed 18 Aug 2021 09:15:29 AM EDT
Install Reason : Installed as a dependency for another package
Install Script : No
Validated By : None
Is there a way to modify the metadata of packages in the local database? Besides changing the "Install Reason", I have not found any related options in the man page for pacman, nor any related information in the Arch Linux documentation for pacman.
Last edited by ricotries (2021-12-08 05:16:25)
Offline
But it is not required by rkhunter: it says as much in the description.
What problem are you actually trying to solve?
Offline
Basically, avoiding some packages from being listed as orphans when they were installed separately on purpose.
If I executed
pacman -Qdt
it will be listed as a "real orphan" since technically no other package depends on it, but yet I did install it to be used by a utility from another package.
Offline
If you want skdet to be a dependency of rkhunter, you need to edit the rkhunter file in the pacman database. But this will revert every update of rkhunter. Other option is to build your own rkhunter package with skdet listed as a dependency - but again, you will need to keep up with the Arch packages.
Offline
Offline
Not 100% what I was looking for, but it helps and I avoid removing packages I deem appropriate.
@Allan I will definitely do more research into what you mentioned to have a better understanding of the package database.
Thank you!
Offline
Another option is to create an empty metapackage that serves no purpose other than listing the packages that you want as dependencies. It's a kludge, but it works.
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline