fix: handle installer errors and avoid Arch partial upgrades

Install Arch dependencies using the existing package database and explain how to recover from stale package metadata. Avoid errexit on the first firmware count, handle Secure Boot prompt EOF as cancellation, propagate error traps into functions, and reject empty firmware sources before modifying installed firmware.

Validation: eight isolated installer regression tests pass; the original installer fails the affected cases. Bash syntax and ShellCheck error-level checks pass. Fixes #100. Addresses the confirmed findings in #108; other audit suggestions remain separate.
This commit is contained in:
Shen Mintao committed 2026-10-19 11:32:32 +08:00
1 parent eef3d25ca4
commit 18a22341ba
3 files changed
+168 -8

No files matched your search

+6
View File
@@ -29,6 +29,12 @@ git clone https://github.com/shenmintao/aic8800d80.git && cd aic8800d80 && chmod
sudo ./install.sh
```
On Arch Linux and derivatives, the installer uses the existing pacman package
database. It does not refresh that database or upgrade the system. If pacman
cannot download dependencies because the database is stale, run
`sudo pacman -Syu` yourself, reboot if the kernel was updated, and rerun the
installer with headers matching the running kernel.
> For more information, please refer to the [README.md](README.md) file.
<br>