Mailinglist Archive: zypp-devel (78 mails)

[Duncan Mac-Vicar Prett <dmacvicar@xxxxxxx>]

On Monday 05 November 2007 08:51:11 you wrote:
> Hence a function "set_policy (struct policies *)" would be completely
> enough.  Where struct policies could look similar to this:
>
> struct policies
> {
>   int (*archchanges) (Solvable *a, Solvable *b);
>   int (*allowdowngrade) (Solvable *a);
>   /* And so on.  */
> };

I had a similar structure in mind.

I think the ruby bindings could implement the ruby part Klaus implemented 
(calling a policy from a ruby function or a ruby file).

What needs to be defined:
- Which policies are needed (like the 2 examples you just said)
- Default policies
- How to specify the policies in the testsuite

Duncan
-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx