omarchy-mac-boot: pin the first-boot manifest check, and say which dependency is Apple-only

Moves the pin to 602266c8, where first boot of a fresh image refuses to finish
without the build manifest that defers its hardware setup. asahi-scripts is
the one Apple-only dependency; the README no longer calls them all generic.
This commit is contained in:
Marcelo Alcantara committed 2026-09-25 20:20:01 +10:00
1 parent 865aaa3f65
commit c48f02942a
2 files changed
+3 -3

No files matched your search

+1 -1
View File
@@ -6,7 +6,7 @@ It follows the fork recipe in maralcbr/omarchy-pkgs (`asahi-quattro`, `pkgbuilds
## Scope
The package is aarch64-only and published to edge only. It widens to rc and stable only after M1 and M2 cold-boot qualification. It depends only on generic packages, and its only provides are the retired Apple-only names, so nothing generic can pull it onto non-Apple aarch64 machines.
The package is aarch64-only and published to edge only. It widens to rc and stable only after M1 and M2 cold-boot qualification. Its only provides are the retired Apple-only names, and nothing generic depends on it or on them, so nothing generic can pull it onto non-Apple aarch64 machines. Its one Apple-only dependency, `asahi-scripts`, comes from the asahi-alarm repository that only the Apple profile configures.
It requires `limine-mkinitcpio-hook` 1.39.0-2 or newer: that is the first build whose hooks leave a Mac's `/boot` to mkinitcpio until Limine is activated. With an older hook, Limine's kernel hook replaces mkinitcpio's by name, and this package's `limine-ready` gate stops it on a Mac that still boots GRUB, so a kernel update would never reach `/boot`.