> You bring up a valid point, and I admittedly haven't given it VERY > much thought yet, but I think that conflicts could be displayed in the > following way: If an instance is unsolvable, then it means that all > possible valuations/assignments make at least one clause (disjunction) > false. Each clause is usually generated by exactly one dependency > specification (the "depends on" directive), so we could print these > dependencies to the screen as suggestions for how to resolve the > conflict. The problem is that might be a lot of entries, e.g. for "depends on PCI" You then end up displaying pages and pages of information, which is very hard to make sense of. You can see that by playing around with libzypp dependencies. -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
