Closed wilsonehusin closed 2 years ago
I think we have an opportunity to solve binary installation in GitHub Actions.
https://github.com/xargs-dev/bindl/blob/2fac2269e78de115b73ba499a1509c42217f555f/.github/workflows/release.yaml#L19-L21
We could possibly have projects declare these dependencies in their bindl configuration, then rely on #10 and add them to $PATH[^1]
$PATH
An inside look on how much bash it takes, courtesy of @puerco.
bash
[^1]: GitHub Actions allows workflows to prepend to PATH, which should be safe to assume that by leveraging it, custom installed binaries will take precedence over pre-existing / system binaries on GitHub Actions runners.
PATH
I think we have an opportunity to solve binary installation in GitHub Actions.
https://github.com/xargs-dev/bindl/blob/2fac2269e78de115b73ba499a1509c42217f555f/.github/workflows/release.yaml#L19-L21
We could possibly have projects declare these dependencies in their bindl configuration, then rely on #10 and add them to
$PATH[^1]An inside look on how much
bashit takes, courtesy of @puerco.[^1]: GitHub Actions allows workflows to prepend to
PATH, which should be safe to assume that by leveraging it, custom installed binaries will take precedence over pre-existing / system binaries on GitHub Actions runners.