Description

The latest release (0.8.0) breaks some of my projects, as it changes the way the dependency resolution is done. The new behavior introduced in #843 causes the versions specified in the main project fpm.toml file not to be respected.

Expected Behaviour

The versions of dependencies specified in the fpm.toml file should be respected as the intended version.

Version of fpm

0.8.0

Platform and Architecture

Linux x86 (but all will observe this behavior)

Additional Information

The intended behavior was that the first time a dependency is encountered (in a breadth first search of the dependency tree), that is the version that should be used. This has the effect that all versions specified in the fpm.toml file of the main project take precedence. The behavior introduced in #843 seems to have inverted this. I.e. the version specified in a dependency gets recorded in the cache, it gets detected as a version update, and it uses that version, meaning the version specified in the main project gets overridden.