FS#35455 - Something like "intent" or "justification"

Attached to Project: Pacman
Opened by Michael Kory Woods (panth0r) - Friday, 24 May 2013, 03:58 GMT
Task Type Feature Request
Category General
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Very Low
Priority Normal
Reported Version 4.1.1
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 2
Private No

Details

Summary 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

Comment by Andrew Gregory (andrewgregory) - Friday, 24 May 2013, 11:51 GMT
This is very similar to https://bugs.archlinux.org/task/8588

It's pretty easy for users to track this type of information on their own without involving pacman.
Comment by Karol Błażewicz (karol) - Friday, 24 May 2013, 11:57 GMT
These kind of notes tend to get pretty elaborate. I often create things like

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.
Comment by Michael Kory Woods (panth0r) - Saturday, 25 May 2013, 03:29 GMT
@Andrew: thanks for referencing that report; for my needs, automating the spirit of this feature request with standard base utilities will be adequate as well as not terribly verbose.

Loading...