dependency leveling?

[Chris Eldredge]

Using openwrap 2.0.2

o list-wrap -IncludeDependencies:

default scope
depends: a = 1.0
a 1.0.0.98114354
depends: b = 1.0
b 1.0.0.98114616
depends: a = 2.0
a 1.0.0.98114354

The last line is obviously problematic, but openwrap does not make any
complaint.

Also, although update-wrap and build-wrap never complain about
divergent dependencies, occasionally add-wrap -System will fail saying
"Package a has conflicting versions". But other times it happily adds
the wrap without complaining. I can't figure out why it sometimes
errors and other times does not.

I know 2.0 is in beta, but what is the expected behavior?

I'm particularly interested in making sure my developers are aware
when the dependency graph diverges so we can avoid preventable runtime
errors.

Thanks,

Chris

[Sebastien Lambla]

Yes there's an issue due to some pull requests that were taken that changed the behavior of the resolver, and we have those issues.

The correct behavior should prevent anything from functioning until the conflict has been resolved.

The reason some of this has been postponed is the current switch to semver means the whole of the versioning stack has been modified, but I'm still working on getting that branch to land qiuckly.

Usually if you want to have more info about how the dependency resolver works, you can have a look at the debug output, there's a whole graph of what is actually going on when resolving. Ideally the data should be available from the command line at some point in the close future.

Seb
________________________________________
From: openwra...@googlegroups.com [openwra...@googlegroups.com] on behalf of Chris Eldredge [chris.e...@gmail.com]
Sent: 19 January 2012 20:32
To: OpenWrap Development Mailing List
Subject: [openwrap-devl] dependency leveling?