Hi! I have merged zypper changes from trunk into the sat branch, and then ported zypper to compile with libzypp. I had some porting steps in wiki Libzypp/SAT_Porting but a nvidia crash sent it to hell before I could save it :-( Some notes: - I submited the packages to zypp:svn project. llibzypp does not build because a weird error after rpm checks for unpackaged files: |RPM build errors: cannot open Pubkeys index using db3 - No such file or directory (2) File not found: /var/tmp/libzypp-4.1.6-build/usr/lib/zypp (anyone knows about this) - the first try, zypper hangs and eats all ram just after loading proxy settings. I unittested the parser and it was OK. So the codepath that comes next, which is something curl proxy related might be causing problems. Renaming sysconfig/proxy away solved this issue. - zypper loads the repos fine, reads rpm database, very fast (9.5 seconds for 18 repos _cold_ time including rpm, that is 10x faster, if I am not lying myself reading the logs in a wrong way), but it can't find the object to install in the pool because the pool iterator is not connected to the SAT pool, this is something Michael is working on. - Right now there is no store for saving patterns and patches. This will be tricky: current store: store --> rpmmd2solv (xml convertor) --> /var/lib/zypp/store.solv -> zypp repo (pool) rpm db ---> rpmdb2solv -----> /var/cache/zypp/_rpm.solv -> zypp repo (pool) The first step of converting the store from xml happens only once, and from rpm every time the rpm db changes. Now, when target reads, we have to load both solvs in the same repo, because sat solver takes only one "installed repo", but later we need to dump the patterns and patches to one solv, while the packages are not dumped (because the primary source is the rpm database ). This requires 2 AIs - integrating repo_write_solv into the library - allowing to save by kind or better: some generic filter) so a solv. This part is _very important_ |- zypper search has to be redone, basically using sat-solver/Repodata search, perhaps we can keep the same interface for now. This is not urgent for the first submit though. | Cheers Duncan | -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org