Mailinglist Archive: zypp-devel (78 mails)

["Duncan Mac-Vicar P." <dmacvicar@xxxxxxx>]

Also, some documentation about how the policy mechanism is supposed to work 
would be nice to allow others to contribute here.

Another comment: policy_exit(), what is the meaning of "exit" here?

The policy_init() seems to allow for a "global" stuff design. Which by 
coincidence is the same reason why you can't use 2 ruby interpreters in the 
same process, because the interpreter instance is invisible, for example, 
what happens if 2 solver objects call policy_init()?

Ho wto solve it, no idea. Only comes to my mind:

Should't the policy engine use a struct with functions, which is used by the 
solver, instead of allocating invisible stuff? Then every policy 
implementation would fill it with the right functions, and the solver could 
ignore them if they are null.

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