Mailinglist Archive: zypp-devel (64 mails)
| < Previous | Next > |
[zypp-devel] package history log file format
- From: Jan Kupec <jkupec@xxxxxxx>
- Date: Thu, 31 Jul 2008 14:40:55 +0200
- Message-id: <4891B2D7.6020604@xxxxxxx>
I've got a mail day, so here's another one :O) We need to decide some
things regarding the $subject.
DATA
According to my research, we need to log these data:
datetime (e.g. YYYY-MM-DD HH:mm:ss format)
action (install | remove | upgrade | downgrade | reinstall)
reqby (auto | user) // meaning requested by - user or dependencies
pkgname
evr
arch
vendor
repo ??? // this is requested, but do we really want it? The vendor
// should be sufficient IMO
oldevr // relevant for upgrades/downgrades
oldarch
oldvendor
oldrepo ???
comments welcome
FORMAT
i suggest a CSV format, one entry per line, with values separated by whatever char, e.g. a pipe, example:
2008-10-12 12:55:03|upgrade|user||0.12.0|i386|suse|dvd11|0.11.9|i386|unknown|somerepo
2008-10-12 12:55:10|remove|user|zypper|0.11.9|i386|unknown|dvd11||||
2008-10-12 12:55:03|install|user|zypper|0.12.0|i386|suse|dvd11||||
This would be machine-readable and still quite human readable.
OTHER ISSUES
The request is that the package history should be human-readable as well as machine-readable. It could as well be two separate logs, one for humans, one for machines.
@Michael (ma): i see you're working on refactoring the zypp commit (?). Please keep in mind that, in case of upgrades/downgrades, we will need also the data of the old solvable from which we upgrade/downgrade there.
cheers,
jano
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
DATA
According to my research, we need to log these data:
datetime (e.g. YYYY-MM-DD HH:mm:ss format)
action (install | remove | upgrade | downgrade | reinstall)
reqby (auto | user) // meaning requested by - user or dependencies
pkgname
evr
arch
vendor
repo ??? // this is requested, but do we really want it? The vendor
// should be sufficient IMO
oldevr // relevant for upgrades/downgrades
oldarch
oldvendor
oldrepo ???
comments welcome
FORMAT
i suggest a CSV format, one entry per line, with values separated by whatever char, e.g. a pipe, example:
2008-10-12 12:55:03|upgrade|user||0.12.0|i386|suse|dvd11|0.11.9|i386|unknown|somerepo
2008-10-12 12:55:10|remove|user|zypper|0.11.9|i386|unknown|dvd11||||
2008-10-12 12:55:03|install|user|zypper|0.12.0|i386|suse|dvd11||||
This would be machine-readable and still quite human readable.
OTHER ISSUES
The request is that the package history should be human-readable as well as machine-readable. It could as well be two separate logs, one for humans, one for machines.
@Michael (ma): i see you're working on refactoring the zypp commit (?). Please keep in mind that, in case of upgrades/downgrades, we will need also the data of the old solvable from which we upgrade/downgrade there.
cheers,
jano
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |