Mailinglist Archive: zypp-devel (64 mails)

< Previous Next >
Re: [zypp-devel] package history log file format
  • From: Klaus Kaempf <kkaempf@xxxxxxx>
  • Date: Thu, 31 Jul 2008 15:49:37 +0200
  • Message-id: <20080731134937.GB31680@xxxxxxxxxxxxx>
* Michael Andres <ma@xxxxxxx> [Jul 31. 2008 15:37]:
On Thu, Jul 31, Duncan Mac-Vicar Prett wrote:

The repository name is not sufficient, as the repository settings can
change over time. Either we need to log those changes as well or we can
use a full URL for the package in the log file.

Each repository can have more than one url. And I am not sure if commit
knows which url was used at the end.

The package can also have been provided by the local package cache or

What's the 'local package cache'.

A 'local package' would have a pathname as the 'repo url'.

A cached package should have a download/cache entry in the log.

built via delta (provided by cache or downloaded).

Then you'd also need a download log, etc.

download url deltafile deltachecksum
applydelta deltafile deltachecksum packagefile packagechecksum
install packagefile packagechecksum

so you can try to figure out how some file came into the system.

Right, "to figure out how some file came into the system" is the main
purpose of the log.


Btw, a proper log would also need a 'rpm database changed' callback
from libzypp if the @system.solv file needs rebuild.
An external program could then log package changes based on comparing
@system.solv (old known state) and the rpm database (new state).


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

< Previous Next >
List Navigation
Follow Ups