![](https://seccdn.libravatar.org/avatar/423e507b7bf71bfc5e4eb0d1177f1ae9.jpg?s=120&d=mm&r=g)
Klaus Kaempf wrote:
* Duncan Mac-Vicar Prett <dmacvicar@suse.de> [Jun 20. 2007 12:27]:
On Wednesday 20 June 2007 11:17:29 Klaus Kaempf wrote:
Can we do reading the rpm database on demand (if changed externally) only ? You need to read it at least once to add the resolvables in the pool.
Which seems to take more time than reading resolvables from the (sqlite) cache.
So how about 'parsing' (resp. caching) the rpm database to the same database all other resolvables are ? (Together with a time stamp or whatever is needed to detect changes).
This would be the first step. And probably easy to do. Another step would be not just simply appending target resolvables to the database, but *merging* them with repository resolvables. That means marking those that match as installed and appending only those that don't match (are installed and are not found in repos). That would speed up search significantly (and maybe solving as well?). But this is something for which we don't have time for 10.3. But what about a feature request for 10.3++?
This way, only the 'refresh' part of libzypp needs to distinguish between repositories with metadata and the rpm database. Applications just init the Repositories (and Pool) without knowing the difference. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org