| 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 = |
|---|
| | 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. |
|---|
| | 3 | Giant 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] |
|---|
