On Wednesday 20 June 2007 17:56, Jiri Srain wrote:
Hi!
This is my suggestion on how to define the refresh policy with refactored ZYPP:
We need to keep the information when last a source was refreshed in order to decide whether a source needs to be refreshed or not. In addition, we will need some policies defining whether a source should be refreshed or not.
RepoManager has a RepoStatus query with timestamp and checksum both for metadata and last cache build. I think I made them private.
2. Tools which should install a package. They should work as fast as possible. we can pay the price of installing package which already has an update at least in some cases.
This assumption is false in most cases. If the metadata is old then what will happen is that you will solve a old package that will probably match (because packages usually doesnt change dependencies often), but the link (filename) will be wrong and the package will fail. This exposes a failure in metadata design, only updating the filenames will be a quite option for the use case you mention. Your usecase works if the repo keeps the old version of the package as well (or more). -- Duncan Mac-Vicar Prett Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org