Let's agree on what a candidate is (installation candidate, right?). Is it one of the resolvables (or pool items) of a Selectable considered to be the most suitable to be selected for installation based on current setup of policies? Is it just a hint for the solver about what should be installed in case the user doesn't specifically choose another version? Is the 'candidate' tied to a particular Selectable or is it rather a candidate of multiple Selectables (the whole pool perhaps)? Klaus suggested the term 'candidate' is misleading. Why? If the candidate is for some reason not installable (which will be determined by solving), is there a problem with still calling it a candidate? Candidate != to-be-installed, right? If the answers are positive, the Selectable::candidate() should return the candidate based on current policies and should be used by the UIs to mark it for installation (if user clicked to install the selectable (no specific version)) and by the solver to mark it for installation to satisfy some dependencies. And that's just about it. If not, please correct me. Anything else? I hope i'm not messing things up :O) -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org