Hi, discussions about sat-solver implementation details over the last days showed that a lot of decisions should not (cannot ?) be hardwired. Instead, a policy should be in place to make solver operation configurable. Revision 7734 of sat-solver now contains a generic policy interface (src/policy.h) and a ruby based policy implementation (src/policy-ruby.c). It currently supports a single policy for demonstration purposes. The goal is to make all policies optional and fast for the default case. I'd be interested in defining a concise list of policies. Input welcome ! Klaus --- SUSE LINUX Products GmbH, 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