Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#35455 - Something like "intent" or "justification"
|
DetailsSummary and Info: It'd be neat to be able to optionally pass a string to pacman containing your reason/s for installing a package. Obviously, this would only act upon newly-installed packages, not upgrades that may also be part of the same installation; for example, assuming Firefox is out of date, running "pacman -Syu [--intent 'chromium\'s libpdf occasionally downloads instead of showing some PDF\'s' evince" will somehow store/bind the "intent" string to Evince but not Firefox.
Whether or not "intent" should be assigned to the already/newly-installed optional/dependencies by default is a bit of a thinker, as a user may use "whoneeds" to determine why, at least dependency-wise, a particularly odd looking package is installed on his or her system and determine the "intent" (perhaps from memory, assumptions made by Arch ["bash is a member of base group"] or the associated "intent" string) of the requiring package. |
This task depends upon
It's pretty easy for users to track this type of information on their own without involving pacman.
After I'm done testing XYZ, '# pacman -Rns foo bar baz'.
Current issues with XYZ:
* blah1
* blah2
...
Check <link to a bug report> and <link to a ML/forum thread> to see if anyone knows how to fix blah2.