The Apple Silicon boot package (Mac initramfs, in-place encryption, first
boot and the Limine activation gate) now builds from packages/omarchy-mac/boot
in omacom/omarchy-mac at a pinned commit: the recipe runs the source's tests
and install staging, and keeps only metadata, backup= and the pacman
scriptlet from the fork recipe. aarch64 and edge only; 20260925-1 upgrades
the fork's 20260921-10. It needs the Apple-gated limine-mkinitcpio-hook
1.39.0-2.
Moving omarchy-hw-platform from omarchy to omarchy-settings loses the file
when the dev pair installs in separate transactions, since omarchy-dev does
not pin omarchy-settings-dev's version. Settings now installs a copy beside
the guard script and omarchy keeps its detector, so no file changes owner.
The settings package's platform guard runs omarchy-hw-platform before the
omarchy runtime is installed. omarchy leaves the detector out of its bin/
loop and settings ships it, with the /usr/share/omarchy/bin link the Apple
predicate and the CLI router use, whenever the source has it.
The guard hook and the script it runs install together from omarchy-settings,
so they are resident before the runtime and hardware packages. Conditional, so
builds from sources without them are unchanged.
On aarch64 the Limine hooks and the mkinitcpio wrapper run through
limine-apple-gate. Only an Apple Silicon Mac (device tree "apple,")
behaves differently: Limine's kernel and removal hooks wait until
Omarchy activates Limine (/var/lib/omarchy/limine.enabled and
/etc/default/limine), mkinitcpio's own kernel hook keeps /boot current
before and after activation, Limine's EFI deploy hook is left to
omarchy-mac-boot, and the wrapper is plain mkinitcpio. Skipped hooks
drain the socket pacman streams targets over.
x86_64 packages exactly what 1.39.0-1 did; generic aarch64 and
Snapdragon keep upstream behaviour.
PR builds link against published edge, so a Hyprland bump in the same merge
cannot see the carry, and as a fast-ring package it would reach every aarch64
channel. The rebuild detection fix that bumps it once the carry publishes
moves to its own PR, so this change only adds the aquamarine carry.
sync-rebuilds followed PUBLISHED_ARCHES (x86_64 by default), so the scheduled
run skipped every aarch64-only package, and it read aarch64 triggers from Arch
Linux ARM even when this repository carries them. It now follows the
architectures a merge builds (CI_ARCHES, shared with build-matrix), and reads a
carried trigger from its recipe once edge publishes that version; until then
its dependents wait. Published databases are verified before use and loaded
once per run.
Carry Arch's aquamarine 0.15.1-1 with one patch that re-reads a connector's
possible CRTCs on rescan, so a Type-C port the Apple DCP fabric reroutes to
another pipeline gets a CRTC without restarting the compositor. aarch64 and
edge only; pkgrel 1.1 sits above Arch Linux ARM's 0.15.1-1.
Bump Hyprland for aquamarine 0.15.1 and make rebuild detection see aarch64.
sync-rebuilds followed PUBLISHED_ARCHES (x86_64 by default), so the scheduled
run skipped every aarch64-only package, and it read aarch64 triggers from Arch
Linux ARM even when this repository carries them. It now follows the
architectures a merge builds, and reads a carried trigger from its recipe once
edge publishes that version.
Packages only packages/omarchy-mac from omacom/omarchy-mac at an exact
quattro-upstream commit, restricted to aarch64 and the edge channel.
Ported from the omarchy-mac/omarchy-pkgs-aarch64 recipe.
Co-authored-by: Scott Jones <scottajones@gmail.com>
A replaces rule applies to any root with the omarchy repo, so a generic
aarch64 system carrying wireguard-arch would be offered this Apple-only
kernel on -Syu. ALARM's linux-aarch64 carries no replaces either.
Ported from the asahi-quattro lane. Both are pinned by hand like
linux-aurora and restricted to aarch64 and the edge channel from their
first merge, since merging publishes. pkgrel sits one above the fork
lanes' builds so the same filename never carries two sets of bytes.
The kernel provided linux=, so on any aarch64 root with the omarchy repo
listed before core, a dependency on linux resolved to this Apple-only kernel
instead of ALARM's linux-aarch64. linux-asahi and WIREGUARD-MODULE stay.
Channel membership narrows to edge until M1 and M2 cold-boot qualification;
promotion widens it again. pkgrel moves to 10 because 7.1.12.aurora2-9 is
already published and a filename is immutable.
qemu-binfmt-conf.sh groups arm with aarch64 and skipped it; Apple Silicon has
no AArch32 execution, so --ignore-family is needed for ARM32 programs. The
bin/sync-upstream extension, its tests and the Tests workflow edit are
reverted; QEMU updates become reviewed pins.
Chromium sandboxes through unprivileged user namespaces on Arch-family
kernels, so the setuid-root helper is unnecessary. The watcher tests now run
from check() as checksummed package sources, leaving tests/ and the shared
Tests workflow untouched.
Marcelo Alcantara