On Tuesday 20 September 2011 15:04:47 Klaus Kaempf wrote:
Oh, I forgot to mention one important property of the xsolvable approach. It gives you the flexibility to create solvables and add them to the pool during runtime. IIRC we dicussed creating patches in libzypp at runtime and the libzypp approach (resulting in a static pool) prevented that.
? The pool is not static, it's global. I.e. we use a single pool, but you are able to change it at runtime. We do this e,g, after commit when rereading the rpm database. Though the public API is focused on loading solv or helix files, you could also inject single solvables. If we have a usecase for this we can also polish the API. The problems will most probably arise at the UI, not in libzypp. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres SUSE LINUX Products GmbH, Development, ma@suse.de GF:Jeff Hawn,Jennifer Guild,Felix Imendörffer, HRB16746(AG Nürnberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org