Personal Omarchy, Hyprland, Emacs, Git, and shell configuration.
git clone git@github.com:mferland/distroconf.git ~/dev/distroconf
~/dev/distroconf/bootstrap.shThe bootstrap is safe to rerun. Before replacing an unmanaged target, it
moves that target into a timestamped directory under
~/.local/state/distroconf/backups/. GNU Stow owns the files in dotfiles/;
the Emacs configuration and launcher are linked explicitly; the SSH client
configuration is installed with mode 0600. The Emacs unit is
installed as a regular file because systemctl reenable removes linked units.
It restores:
- user-owned Arch and AUR package selections;
- Hyprland look-and-feel, including fully opaque windows;
- Omarchy shell layout, default agent, theme, font, and background;
- reviewed Omarchy shell plugins pinned in
plugins/omarchy.tsv; - Git and shell configuration;
- Emacs configuration and local modes;
- SSH-agent integration and the Emacs user service;
- the
editEmacs launcher in~/bin.
Generated Omarchy theme files, caches, private keys, browser data, Wi-Fi credentials, and machine-specific system configuration are deliberately not tracked. Privileged or hardware-specific setup remains documented in the Org files; omarchy.org documents the optional workstation setup.
- Omarchy overview: managed configuration and optional setup.
- Disk swap: RAM-sized Btrfs swap, activation, and verification.
- Hardware: optional keyboard firmware mapping.
- SSH: client keys, the user agent, Git hosts, and optional server setup.
- YubiKey: security-key enrollment, SSH connection reuse, PAM, and smart-card integration.
- Network mounts: home NAS over NFS and work SAPFS over CIFS.
- kas and Podman: rootless Yocto builds with writable repositories.
- Emacs integrations: optional RTags setup.
- VM testing: installation, iteration, diagnostics, and acceptance checks.