Leave agents/ ready for other agent artifacts like definitions and prompts alongside the skills. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1.5 KiB
1.5 KiB
Install Scripts
Read this before working under install/ or on the system/user setup commands.
The ISO owns installation orchestration. This repo ships target-side setup commands and reusable setup leaves:
bin/omarchy-setup-systemruns root-owned system setup during ISO finalization.bin/omarchy-setup-hardwareruns idempotent hardware-specific setup and is called byomarchy-setup-system.bin/omarchy-finalize-userruns the per-user runtime finalization (skill symlinks, xdg-user-dirs, mime defaults,install/user/all.sh). Shipped user defaults are seeded by/etc/skelfromomarchy-settings, not by this command.bin/omarchy-reinstall-configsis the explicit destructive resync of those defaults into an existing user's$HOME.- leaf scripts under
install/are sourced byrun_logged $OMARCHY_INSTALL/path/to/script.shand intentionally do not have shebangs. - avoid
exitin sourced setup scripts unless intentionally aborting setup. - use
$OMARCHY_INSTALLand$OMARCHY_PATHinstead of hard-coded Omarchy paths. - keep root-scoped hardware setup under
install/hardware/and orchestrate it throughinstall/hardware/all.sh. - keep every per-user setup leaf under
install/user/(includinginstall/user/hardware/andinstall/user/first-run/) so it is clear what must run for each user. - prefer helper commands for package and command checks where available.
Raw command -v, pacman, and pacman-key are acceptable in package-helper
contexts where direct package-manager behavior is the point of the script.