Mailinglist Archive: zypp-devel (64 mails)

[Klaus Kaempf <kkaempf@xxxxxxx>]

* Jan Kupec <jkupec@xxxxxxx> [Jul 31. 2008 16:24]:
> Klaus Kaempf wrote:
> > * Jan Kupec <jkupec@xxxxxxx> [Jul 31. 2008 14:43]:
> > > datetime (e.g. YYYY-MM-DD HH:mm:ss format)
> > > action   (install | remove | upgrade | downgrade | reinstall)
> > - What's 'reinstall' supposed to be ?
> zypper in --force (rpm -i --force i guess). I guess this should be logged a 
> separate action (?).

I do not think this is needed. In the end, this is just a package
install.

> > - 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.

Agreed. However, reading and parsing name-evr.arch is well established.

> > - '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.

Well, all changes to the rpm db can be logged since @system.solv gives
you the last 'valid' state. External package installs/updates will
miss the repo and user, though.

> > - 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).

Stano brought up a good point on why dependency information is useful:
Product and pattern removals. If a package is installed due to a
pattern or product, keeping this relation information helps in
removing the product or pattern.

The yast2-users maintainer should know the policy about unix user
names ;-)

Klaus
-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx