Wrong binary is installed when there are multiple files with same binary basename

[dieddc]

Example tool fd

installing this on amd system will choose the asset fd-v10.1.0-x86_64-unknown-linux-gnu.tar
This archive has the files:
fd 4Mb is the correct binary
fd.1 17k, not a binary

When installing this the second file will be installed.

current config:

  fd:
    description: A simple, fast and user-friendly alternative to 'find'
    url: https://github.com/sharkdp/fd/
    list:
      type: github-releases
      url: https://api.github.com/repos/sharkdp/fd/releases
    fetch:
      url: https://github.com/sharkdp/fd/releases/download/v{{ .Version }}/fd-v{{ .Version }}-x86_64-unknown-{{ .OS }}-gnu.tar.gz
    install:
      type: tgz
      binaries:
        - fd

[dieddc]

Found the solution for this problem.
It's possible to enter a regexp value for binaries.
In this case the solution is

    install:
      type: tgz
      binaries:
        - "^fd$"

[leucos]

Yes indeed. Thanks for reporting. Would you like to send a PR ?

[eagafonov]

I think I found the root cause of the issue.

Here is the commit that updates filename matching:

d134901#diff-dc056a335c80610e7d7f9affa1d47685f4624e15a14c8031b7d854546a10bbd6

It replaced strings.HasSuffix with regexp.MatchString

PS: https://xkcd.com/208/

[eagafonov]

JFYI: Similar problem with micro

#269