Mailinglist Archive: zypp-devel (78 mails)
| < Previous | Next > |
[zypp-devel] Sat-Solver policy engine
- From: Klaus Kaempf <kkaempf@xxxxxxx>
- Date: Thu, 1 Nov 2007 15:33:23 +0100
- Message-id: <20071101143323.GA17303@xxxxxxxxxxxxx>
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@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
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@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |