Bug 1235901

Summary: Add description to a dnf transaction
Product: [Fedora] Fedora Reporter: Peter Tselios <ptselios>
Component: dnfAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: jsilhan, mluscon, packaging-team-maint, pnemade, rholy, tim.lauridsen, vmukhame
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-26 11:25:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Peter Tselios 2015-06-26 04:25:22 UTC 
Description of problem:
when you search the history, you can see the timestamp of the action, the action itself and the number of packages included in the transaction. However, you have no information about it. What was the original command, or why you installed that package. 

For example, it would be great to use dnf history list and have a list like the following:

ID     | Description          | Date a           | Action  | Altere  | User 
-------------------------------------------------------------------------------
...
4001   | Change Control #1233 | 2014-06-24 09:01 | Install |    8  < | Me
4000   | Install oVirt        | 2014-06-24 09:01 | Install |    8  < | Me
...

That could be implemented with a "--description" directive in the dnf [install
erase] action, like for example:

dnf install oVirt --description "Install oVirt"
dnf install package123 --description "Change Control #1233"
Comment 1 Honza Silhan 2015-06-26 11:25:51 UTC 
I believe this is a duplicate. Now you are the second person requesting this feature. It could be handy in layered images too, to see what packages were installed in which image from running container. Maybe you want a little more helpful output of history list too (bug 1218401).

*** This bug has been marked as a duplicate of bug 1192684 ***