On Friday 09 November 2007 15:42:12 Martin Vidner wrote:
Like (B), but separate the decision code from the solver. I see a single interface point now:
policy->get_boolean("prefer_arch_over_version")
Actually most of the decisions in the solver are taken in the same way, so the solver has a list of canddates, and it choses something. If you don't want to allow downgrades, you just remove the lower versions from the list before the solver will use it, you can remove different architectures, vendors etc. The boolean approach is configuration. The policy itself will mostly get a list of solvables, and filter over them. The boolean values can be used by the policy to know what to filter. But that is not part of the solver, which will of course offer some default policy and functions to filter (so the code does not propagate from the solver complex algorithms to the policies itself) Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org