diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-17 14:36:57 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-17 14:36:57 -0500 |
| commit | 79f027d4fa8a0e5abb32c6cf8c21586b73c77a39 (patch) | |
| tree | 7441b19219e23ba77b131da0cecf1fd43d52232e /scripts/testing/setup-testing-env.sh | |
| parent | 19cd3ffad4874a812fb5ecbff636e15b0d0a7fc7 (diff) | |
| download | archsetup-79f027d4fa8a0e5abb32c6cf8c21586b73c77a39.tar.gz archsetup-79f027d4fa8a0e5abb32c6cf8c21586b73c77a39.zip | |
refactor(scripts/games): array + loop, flathub remote check, failure summary
Three things were wrong with the old script:
- One line had a duplicate `flathub` argument (`flatpak install ...
flathub flathub org.gnome.Crosswords`). Flatpak tolerated it; still
a typo.
- Nothing added the flathub remote, so a fresh machine without it would
fail on every line.
- 24 nearly identical `flatpak install` lines with no central handling
if one app failed.
I moved the app IDs into a single `APPS=()` array (sorted) and looped.
The script now runs `flatpak remote-add --if-not-exists --user flathub
https://flathub.org/repo/flathub.flatpakrepo` up front, collects any
failed apps into a `failed` array, and prints a summary plus a non-zero
exit at the end if anything didn't install. I used `set -uo pipefail`
rather than `-euo` on purpose so a single failed install doesn't abort
the rest of the run.
Diffstat (limited to 'scripts/testing/setup-testing-env.sh')
0 files changed, 0 insertions, 0 deletions
