Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict Resolution Strategy - Incumbent Dependency Downgrade #17

Open
brendanjerwin opened this issue Sep 19, 2010 · 0 comments
Open

Comments

@brendanjerwin
Copy link

See "Dependency Version Leveling"

If the conflicting package is itself a dependency of another package, like NHibernate in our example, the next approach that Nu can try is to see if, by downgrading the conflicting package, it can find a compatible set. In this case, Nu will attempt to downgrade NHibernate, within the dependency requirements of all packages which depend on it, until it finds a compatible set or runs out of available options. For each compatibility check Nu will execute the entire stack of rules, i.e. it will first look for Dependency Version Overlap, and then attempt to downgrade Castle Windsor using Newcomer Downgrade. If Nu is able to find a workable set here it will also do so automatically, since the downgrades were within the declared compatible versions of the installed package (Fluent NHibernate).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant