Changes between Version 3 and Version 4 of YumTsDb

Show
Ignore:
Author:
james (IP: 65.172.155.230)
Timestamp:
08/28/09 15:42:24 (8 years ago)
Comment:

Update to reflect what has happened atm.

Legend:

Unmodified
Added
Removed
Modified
  • YumTsDb

    v3 v4  
    1 = this is a draft for a yum transaction database = 
    2 the idea is to keep track of all the info of what happened during a  transaction, what caused it, the commands which invoked it, the state of things when it was invoked, etc 
     1= this is a draft for a yum history (of transactions) database = 
     2the idea is to keep track of all the info of what happened during a  transaction, what caused it, the commands which invoked it, the state of things when it was invoked, etc. 
     3Giant patch currently available: http://james.fedorapeople.org/yum/patches/history-BIG.patch ... also in my yum git repo. (history branch). 
     4 
     5== things current history patch does == 
     6 * yum nevra+pkgId 
     7 * nevra + checksums in the rpmdb before the ts (kind of, uses rpmdb version). 
     8 * nevra + checksums after the ts 
     9 * package dependencies/relationships within the ts? 
     10   * the proposed actions in the ts 
     11   * the proposed actions in the ts broken down into install/remove te's (we kind of save the TS_STATE) 
     12 * result/errorcode  of the ts run 
     13 * getloginuid() -- something so that different users doing "sudo yum blah" could be differentiated? 
     14 * timestamp of the operation 
     15 * duration 
     16 * undo/repeat API and commands 
     17 * list/info/summary commands 
     18 
     19== things current history patch almost does == 
     20 * all the enabled plugins (nevra+pkgId) -- [We need an API to allow things to add packages to the "transaction performed with packages" list] 
    321 
    422 
    5 == things to track == 
     23== things to maybe track == 
    624 * yum.conf.* 
    725 * all the repos enabled and timestamps/checksums of their repomd.xml files 
    8  * all the enabled plugins (nevra+pkgId) 
    9  * yum nevra+pkgId 
    1026 * all the cli options (if any) 
    11  * nevra + checksums in the rpmdb before the ts 
    12  * nevra + checksums after the ts 
    13  * package dependencies/relationships within the ts? 
    14  * the proposed actions in the ts 
    15  * the proposed actions in the ts broken down into install/remove te's 
    1627 * any/all logging output from the ts (tricksy) 
    17  * result/errorcode  of the ts run 
    18  * timestamp of the operation 
    19  * getuid(), getloginuid()? -- something so that different users doing "sudo yum blah" could be differentiated? 
    20  * duration 
    2128 
    2229This is part of the YumProposedDbs page 
     30 
     31Updated: 2009-08-28