FS#75283 - Feature: 'Build dependency' Install Reason

Attached to Project: Pacman
Opened by Gwynne (gwynne) - Saturday, 09 July 2022, 23:49 GMT
Last edited by Allan McRae (Allan) - Sunday, 04 December 2022, 02:15 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 6.0.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
Mainly used when building packages through the AUR and yay. Add a third Install Reason for packages to inform the user that a package was installed for building another package

Reason:
Currently such build denpendencies are considered orphans in the eyes of pacman. Yay even asks me if I want to keep the build dependencies, but when I run the classic `pacman -Qtdq | pacman -Rns -` from time to time all those packages get cleared as well. This feature would be great to remove orphaned packages without deleting build dependencies.

Maybe another category like 'Required by' would be nice too, to see what that package is the build tool for.
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 04 December 2022, 02:15 GMT
Reason for closing:  Won't implement
Comment by Andrew Gregory (andrewgregory) - Tuesday, 12 July 2022, 16:02 GMT
I am not particularly a fan. If you want to keep build deps around between builds, I think that's better accomplished with a metapackage that depends on them, e.g., you have package foo and foo-build-deps. Then all of pacman's existing tooling just works normally. I'm sure tools like yay could easily automate this.

Loading...