resolve priorities

[Milen Dyankov]

Say I have a bundle that 

 - imports a package P

 - requires capability C

If none is present and I try t resolve it, it has 2 reasons to fail - can't find the package and unsatisfied requirement. 

Is there any way to influence in which order those are checked? In another words, can I somehow make sure that the error is "can not resolve C" and not "can not find P"? If not can I somehow get both?

Best,

Milen

[Peter Kriens]

You cannot get both nor can you control the order … The resolver tries all combinations and then gives up on one of the potentially many paths it could take.

To find problems, I generally try to first resolve a bundle on its own and then its requirements one by by one. It would be nice if someone could improve this UI. I once had a discussion with Neil to check each repository entry against the current repository. He made the changes in the GUI to make it possible to show a red, yellow, or  green light but I never got around to do the resolve work to know this state.

Ah well, wonders of open source …

Kind regards,

Peter Kriens

--
You received this message because you are subscribed to the Google Groups "bndtools-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bndtools-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.