Mailinglist Archive: zypp-devel (78 mails)
| < Previous | Next > |
Re: [zypp-devel] Sat-Solver policy engine
- From: Duncan Mac-Vicar Prett <dmacvicar@xxxxxxx>
- Date: Mon, 5 Nov 2007 16:33:06 +0100
- Message-id: <200711051633.06828.dmacvicar@xxxxxxx>
On Monday 05 November 2007 16:23:28 Klaus Kaempf wrote:
That is exactly what Michael is trying to prevent. A new plugin mechanism.
Basically the idea is just to offer callback interface, and the application
using the solver would implement them. No need for config files or plugins.
The ruby bindings could implement them, gluing them to a ruby file with
functions. While ZYpp could glue them to its own config file AND/OR UI
iteraction.
What we need now, is the list of policies, to design that interface, and
again, any idea on how to keep the testsuite running when the policies are
not longer constant.
Duncan
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
Time for a '/etc/solver.conf' file or a /etc/solver/policy directory
to place a .so file with the policy implementation ?
That is exactly what Michael is trying to prevent. A new plugin mechanism.
Basically the idea is just to offer callback interface, and the application
using the solver would implement them. No need for config files or plugins.
The ruby bindings could implement them, gluing them to a ruby file with
functions. While ZYpp could glue them to its own config file AND/OR UI
iteraction.
What we need now, is the list of policies, to design that interface, and
again, any idea on how to keep the testsuite running when the policies are
not longer constant.
Duncan
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |