Updating Your Config
Config updates are merged with what's already in $HOME, not copied over it. The same mechanism runs on first boot and every time you ask for it later.
Sobarch's default dotfiles live in a package (sobarch-skel) rather than being copied once and forgotten. Every time it's applied, whether on first boot or whenever you ask for it afterward, it merges into your $HOME using a three-way comparison for each file:
- Your current copy in
$HOME - The baseline, a record of what was applied last time
- The new version being deployed
A file merges automatically wherever only one side actually changed. When both your copy and the new version changed the same file, that's a genuine conflict: the new version is dropped next to it as <file>.sobarch-new, and your real file is never touched.
Running it yourself
From the desktop: Super → Sobarch → Update Config. Before merging, it refreshes the sobarch-skel/sobarch-scripts packages themselves via the package sync mechanism and re-applies boot and login theming, so branding changes ship through this same command as config changes. It then rebuilds your tinty templates, runs the merge described above, and walks you through any conflicts interactively: Keep yours, Use the new version, view the Diff, Edit, or Skip for now.
If you'd rather just revisit conflicts left over from a previous run without re-checking everything else, use Review Conflicts instead. It re-runs the same interactive walkthrough over whatever .sobarch-new files are still sitting on disk.