Skip to content

omarchy-settings-dev: ship the platform guard on aarch64 only - #691

Merged
maralcbr merged 1 commit into
masterfrom
settings/platform-guard-aarch64-only
Sep 28, 2026
Merged

maralcbr merged 1 commit into
masterfrom
settings/platform-guard-aarch64-only

Conversation

@maralcbr

@maralcbr maralcbr commented Sep 28, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • omarchy-settings-dev installs the pacman platform guard's hook, script and detector copy only when CARCH is aarch64. pkgrel 2 → 3.
  • No platform package is built for x86_64, and pacman refuses another architecture's package there anyway, so the guard only cost x86 a read of the sync databases on every transaction. The x86 HOOKS baseline keeps the busybox line without a detector, so the detector copy isn't needed there either.
  • omarchy-settings gets the same two lines in omarchy-settings: ship the full set on aarch64 for runtime-profile sources #638, so it publishes once.

Follows review of omacom/omarchy#13362, which treats a missing guard on x86 as expected.

Test plan

  • CI builds omarchy-settings-dev on x86_64 and aarch64
  • With a source that carries the guard: the aarch64 package has the three /usr/share/libalpm/{hooks,scripts}/ files and the x86_64 package doesn't

@maralcbr

Copy link
Copy Markdown
Collaborator Author

Draft until #638 lands. CI is red because the recipes change without a pkgrel bump, so the planner builds nothing. After #638 merges, this rebases with omarchy-settings pkgrel 5 and omarchy-settings-dev pkgrel 3. #638's runtime-profile test already expects the guard on aarch64 only.

@maralcbr
maralcbr force-pushed the settings/platform-guard-aarch64-only branch from e4e41fd to a5bfaba Compare September 28, 2026 03:40
@maralcbr maralcbr changed the title omarchy-settings: ship the platform guard on aarch64 only omarchy-settings-dev: ship the platform guard on aarch64 only Sep 28, 2026
@maralcbr
maralcbr marked this pull request as ready for review September 28, 2026 03:40
No platform package is built for x86_64 and pacman refuses another architecture's package there, so x86 transactions gain nothing from the guard. The x86 HOOKS baseline keeps the busybox line without a detector, so the detector copy goes too. omarchy-settings gets the same change in #638.
@maralcbr
maralcbr force-pushed the settings/platform-guard-aarch64-only branch from a5bfaba to 7f77d82 Compare September 28, 2026 03:40
maralcbr added a commit that referenced this pull request Sep 28, 2026
No platform package is built for x86_64, so an x86 machine has nothing to
guard. The check that 00-omarchy-hooks.conf has its detector copy follows it:
without the copy, x86_64 keeps the busybox line it would have anyway, and
leaving the check unscoped would fail every x86_64 build from a source that
asks omarchy-hw-platform. Taken from #691, which keeps the -dev recipe.
@maralcbr
maralcbr merged commit a701a8d into master Sep 28, 2026
7 checks passed
spencerbull pushed a commit to jacob-vincent-mink/omarchy-pkgs that referenced this pull request Sep 28, 2026
The guard and its detector copy now ship on aarch64 only (omacom#691), so the check that 00-omarchy-hooks.conf has its detector failed every x86_64 build from a source that carries the HOOKS baseline. x86_64 keeps the busybox line without a detector. Same scoping as omarchy-settings in omacom#638.
jethrojones pushed a commit to jethrojones/omarchy-pkgs that referenced this pull request Sep 28, 2026
…e sources

omacom#638 gave omarchy-settings this and -dev was never ported, so edge, the only
channel aarch64 machines are qualified for, still stripped zram, oomd, zswap,
the sysctl tuning and USB autosuspend there: on Snapdragon, migration
1790328426 installs zram-generator, finds no dev-zram0.swap and completes
without zram. A source with default/settings-runtime-profile now gets the same
files, backup and optdepends on aarch64 as on x86_64, Thunderbolt drop-in
included, and its HOOKS files ship as they are. Older sources, including the
current quattro pin, keep today's aarch64 package. The platform guard and its
detector check stay aarch64-only (omacom#691, omacom#694). The keyboard backlight unit
first-run enables ships whenever the source has it, as in omarchy-settings.

tests/settings-runtime-profile.sh now runs both recipes. pkgrel 5 so the
recipe change builds; the payload from the current pin is unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant