alr run with ambiguous bins

[reznikmm]

Hello!

I found strange messages from alr run after creating a crate for libadalang_tools:

max@untu:/tmp/libadalang_tools_23.0.0_ccffc4dd$ ~/bin/alr run --list
Crate libadalang_tools builds these executables:
   gnatmetric
      (found at /tmp/libadalang_tools_23.0.0_ccffc4dd/bin/gnatmetric)
      (found at /tmp/libadalang_tools_23.0.0_ccffc4dd/bin/gnatmetric)
...

Looks like the candidate list is incorrect. Then, I tried:

max@untu:/tmp/libadalang_tools_23.0.0_ccffc4dd$ ~/bin/alr run gnatmetric
...
error: Too many candidates found:
/tmp/libadalang_tools_23.0.0_ccffc4dd/bin/gnatmetric
/tmp/libadalang_tools_23.0.0_ccffc4dd/valgrind/gnatmetric

This candidate list is correct, I guess.

Alr version: 1.1.0

[mosteo]

Thanks, Maxim. I guess the list is computed correctly but in the first instance it is wrongly printed.