How to install / to configure if released tarballs contain two or more binaries?

[lupo-on-github]

The tarballs released for scrcpy contain two binaries,

• scrcpy
• scrcpy-server

The second is mandatory [1].

But it seems to be ignored.

Is this happening because

• it is a second binary in the tarball, or
• alone because it is not marked as executable [2]?

---

[1] scrcpy pushes scrcpy-server to an Android device,
where it is executed.

[2] Even if registered in config.yaml seperately as binary to install,
binup seems to refuse to download it, complaining that it is not
marked as executable.

[KonishchevDmitry]

1. If release file contains more than one binary, in terms of binup it's multiple applications that should be configured/installed separately. Here is an example of how I install various VictoriaMetrics tools which are packaged in a single archive:

  vmagent:
    project: VictoriaMetrics/VictoriaMetrics
    changelog: https://docs.victoriametrics.com/CHANGELOG.html
    release_matcher: ~^vmutils-linux-amd64-v(\d+\.){3}tar\.gz$
    binary_matcher: vmagent-prod
    post: systemctl restart vmagent.service

  vmalert:
    project: VictoriaMetrics/VictoriaMetrics
    changelog: https://docs.victoriametrics.com/CHANGELOG.html
    release_matcher: ~^vmutils-linux-amd64-v(\d+\.){3}tar\.gz$
    binary_matcher: vmalert-prod
    post: systemctl restart 'vmalert@*.service'

  vmbackup:
    project: VictoriaMetrics/VictoriaMetrics
    changelog: https://docs.victoriametrics.com/CHANGELOG.html
    release_matcher: ~^vmutils-linux-amd64-v(\d+\.){3}tar\.gz$
    binary_matcher: vmbackup-prod

  victoria-metrics:
    project: VictoriaMetrics/VictoriaMetrics
    changelog: https://docs.victoriametrics.com/CHANGELOG.html
    release_matcher: ~^victoria-metrics-linux-amd64-v(\d+\.){3}tar\.gz$
    post: systemctl restart 'victoria-metrics@*'

2. In your case you actually have the following:

• adb and scrcpy binaries, which you can install in the same manner as in example above.
• scrcpy-server which is actually not an executable binary (application) – it's apk (package). So it's a related resource for scrcpy which is not supported by binup – at this time it supports single binary apps only which doesn't require any additional resources (which makes installation/upgrade rules clear and understandable).

The only thing I can recommend now, is to workaround the issue in post script:

post: |
  set -eu
  set -o pipefail
  version="$(/usr/local/bin/scrcpy --version 2>&1 | head -n1 | cut -d' ' -f2)"
  curl --fail --location "https://github.com/Genymobile/scrcpy/releases/download/v$version/scrcpy-linux-x86_64-v$version.tar.gz" | tar -C /usr/local/lib -xz --wildcards '*/scrcpy-server' --transform 's/.*/scrcpy-server/' --no-same-owner 

[AndreiCherniaev]

In workaround you should not hard-code ARCH as "linux-x86_64". See examples