]> _ Git - alire.git/commit
Show linked paths and per-release dependencies (#453)
authorAlejandro R Mosteo <alejandro@mosteo.com>
Wed, 24 Jun 2020 21:08:17 +0000 (23:08 +0200)
committerGitHub <noreply@github.com>
Wed, 24 Jun 2020 21:08:17 +0000 (23:08 +0200)
commita9be861ab640ac79a96b0995ed00dfb58766ccf8
treedd3998d3a44937dd2a7df3529dfe175e5cea79af
parent85f2fe3fdcde74990dd3acd492e1310f63611a45
Show linked paths and per-release dependencies (#453)

In the graph section of the solution printout, the concrete dependency for each
release that brings in another release is now shown. This may help in
understanding why a release is chosen, particularly when there are different
restrictions on a same crate introduced by different releases.

For the new linked folders with alire metadata, the source folder is shown in
the releases section. Otherwise, such source folders are listed in the
externals section without a concrete release (as we cannot determine a version
for them).

A new test shows this feature and also shows that the solver is able to
downgrade a dependency whenever this is needed to obtain a complete solution.
doc/user-changes.md
src/alire/alire-dependencies-graphs.adb
src/alire/alire-solutions.adb
src/alire/alire-solutions.ads
testsuite/fixtures/solver_index/su/superhello.toml [new file with mode: 0644]
testsuite/tests/solver/one-dep-two-constraints/test.py [new file with mode: 0644]
testsuite/tests/solver/one-dep-two-constraints/test.yaml [new file with mode: 0644]