Mailinglist Archive: zypp-devel (64 mails)
| < Previous | Next > |
Re: [zypp-devel] package history log file format
- From: Jan Kupec <jkupec@xxxxxxx>
- Date: Thu, 31 Jul 2008 16:24:49 +0200
- Message-id: <4891CB31.9080309@xxxxxxx>
Klaus Kaempf wrote:
OK, makes sense.
OK, makes sense, too. Let's see what comes out of the 'package origin' discussion.
OK
OK
I meant this to be more easily parsable. It's harder to parse name-evr.arch, than have these already separated by the line reader.
OK, each action will have it own well-defined set of columns.
I see no problem with that. Just i side note, any package installed
by external tools and not logged will be considered as installed by
(unknown) user; for whatever purpose like auto-removal of unused packages.
Neither do i :O) But it might be a problem to distinguish the user name from a pacakge-evr.a, or not (i don't know what's the policy about unix user names).
agreed
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
* Jan Kupec <jkupec@xxxxxxx> [Jul 31. 2008 14:43]:zypper in --force (rpm -i --force i guess). I guess this should be logged a separate action (?).
datetime (e.g. YYYY-MM-DD HH:mm:ss format)- What's 'reinstall' supposed to be ?
action (install | remove | upgrade | downgrade | reinstall)
reqby (auto | user) // meaning requested by - user or dependencies
It should be the real username, remember we want to be role-based in
the future. Probably with a '@hostname' to cope for remote
administration.
OK, makes sense.
repo ??? // this is requested, but do we really want it? The vendor
// should be sufficient IMO
The vendor can be faked. IMHO, the repository url is needed here.
(There is no need to repeat the complete repo url for hundreds of
packages. A single "repo #3 is http://...." log entry and referencing
the repo as '#3' is less verbose.
OK, makes sense, too. Let's see what comes out of the 'package origin' discussion.
Some suggestions:
- make the action a fixed length, its easier to read
OK
- move the 'user' towards the end, the package is more important
information.
OK
- don't split name, evr and arch into separate columns. name-evr.arch
is a quite common notation.
I meant this to be more easily parsable. It's harder to parse name-evr.arch, than have these already separated by the line reader.
- have a flexible number of columns, improves readability
OK, each action will have it own well-defined set of columns.
- 'auto' could be eliminated, everything without a user is 'auto'
I see no problem with that. Just i side note, any package installed
by external tools and not logged will be considered as installed by
(unknown) user; for whatever purpose like auto-removal of unused packages.
- We could include dependency information by putting a package into
the 'user' column. Don't know how useful this actually is
Neither do i :O) But it might be a problem to distinguish the user name from a pacakge-evr.a, or not (i don't know what's the policy about unix user names).
Example:
2008-10-12 12:55:03|repo|1|dvd11
2008-10-12 12:55:03|update
|libzypp-1.42-39.i586|libzypp-1.27-63.i586@1|root@localhost
2008-10-12 12:55:10|remove |zypper-0.11.9.i386|pope@vatican
2008-10-12 12:55:03|install|libzypp-1.43.0.i586@1
Alternative: 2008-10-12
12:55:03|install|libzypp-1.43.0.i586@1|zypper-0.12.0.i586@1
2008-10-12 12:55:03|install|zypper-0.12.0.i586@1|root@xxxxxxxxxxx
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.
Well, the 'human readable' should be 'admin readable'. I don't see the
need for a 'natural language' but a nicely structured, line based
format in a single(!) log file.
agreed
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |