Bug 1192684 - RFE: history transaction labels
Summary: RFE: history transaction labels
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf-plugins-core
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1235901 (view as bug list)
Depends On: 1167239
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-14 06:08 UTC by Pete Travis
Modified: 2015-06-26 11:25 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-03-05 14:12:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pete Travis 2015-02-14 06:08:28 UTC
If I run a package transaction and later want to undo the transaction with `dnf history`, it can be a time consuming process to iterate over `dnf history info N` to identify the transaction later.  It would be helpful if I could arbitrarily label a transaction and have the label show as a column in the history list, for example:

    dnf install gnumeric calligra-sheets libreoffice-calc --historylabel spreadsheets
    
    # test the applications

    dnf history 

ID     | Label        |Login  | Date a           | Action         | Altere
---------------------------------------------------------------------------
   246 | spreadsheets | Pete  | 2015-02-13 22:55 | I, U           |    4  

    dnf history undo 246 (or) dnf history undo --historylabel=spreadsheets --exclude-libreoffice-calc

Comment 1 Honza Silhan 2015-03-05 14:12:45 UTC
Hi, this could be work for some plugin. We need the new history database that would allow to save custom values and expose it's API. I am not convinced that this RFE will not be massively used. At the time of installation you don't usually know that you would like to at the future undo that and for that case tag it. If anyone comes with new use case, feel free to share it.

Comment 2 Honza Silhan 2015-06-26 11:25:52 UTC
*** Bug 1235901 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.