* Duncan Mac-Vicar P.
I am quite surprised that you find this a bug, when you had to do exactly the same once and invent xsolvable. ZYpp just took a different path and prefered to manage one pool instead of adding one Pool pointer to each solvable.
The difference is that satsolvevr-bindings allows direct access to the underlying satsolver while libzypp does not. At least, thats my understanding.
If the sat-solver would offer a string pool shared across multiple pools, it would be cool to get rid of global objects, and IdString could have only a global string pool.
Whats the use-case for multiple pools ?
The API we have been discussing tries to hide the fact that there are global objects. Even if they are, you use your own handler.
Then we're in complete agreement as I'm not aware of any global objects used in satsolver-bindings. Klaus --- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org