thomas.koppandClaude Opus 5
d215dfefc5
master still carried the 2021 tree. Task 6 does a checkout over $HOME, so nine of those files would have overwritten the current configuration rather than updated it - i3, sway, dunst, nvim, vim and tmux, all diverged by years. The plan had no step for this; the design warned about it and then nothing implemented the warning. The nine are now taken from the live machine verbatim, and the 31 files with no counterpart there are dropped. Everything remains on archive/2021-i3-sway. README.md and .scripts/install.sh are kept despite having no live counterpart: the first documents the repository and the second is what ls.shron.de/dotconf serves, so deleting it would break that link. Verified byte-identical to the live files afterwards, which is the point - a checkout on this machine must change nothing. KDE has been in daily use for a while with nothing backing it up. Eighteen rc files and the nine autostart entries are added: window rules and shortcuts, notification behaviour, the lock screen, and the panel layout in plasma-org.kde.plasma.desktop-appletsrc. That last one is rewritten by plasmashell whenever anything moves, so it will produce churn - kept anyway, since a lost panel layout is the most tedious thing here to rebuild by hand. .config/kdeconnect/ is excluded rather than added. It holds the device certificate and its private key, and is pairing state rather than configuration - the only place under .config that carries a secret. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
DISCLAIMER:
this is not my work I've the idea from https://developer.atlassian.com/blog/2016/02/best-way-to-store-dotfiles-git-bare-repo/
In his words the technique below requires:
No extra tooling, no symlinks, files are tracked on a version control system, you can use different branches for different computers, you can replicate you configuration easily on new installation.
but for reason: ;)
- git and
- curl
How it work
The technique consists in storing a Git repository in a "side" folder (like $HOME/.cfg or $HOME/.myconfig) using a specially crafted alias so that commands are run against that repository and not the usual .git local folder, which would interfere with any other Git repositories around. Starting from scratch
If you haven't been tracking your configurations in a Git repository before, you can start using this technique easily with these lines:
git init --bare $HOME/.cfg
alias config='/usr/bin/git --git-dir=$HOME/.cfg/ --work-tree=$HOME'
config config --local status.showUntrackedFiles no
echo "alias config='/usr/bin/git --git-dir=$HOME/.cfg/ --work-tree=$HOME'" >> $HOME/.bashrc
The first line creates a folder ~/.cfg which is a Git bare repository that will track our files. Then we create an alias config which we will use instead of the regular git when we want to interact with our configuration repository. We set a flag - local to the repository - to hide files we are not explicitly tracking yet. This is so that when you type config status and other commands later, files you are not interested in tracking will not show up as untracked. Also you can add the alias definition by hand to your .bashrc or .zshrc or use the the fourth line provided for convenience.
I packaged the above lines into a snippet up. So that you can set things up with:
curl -Lks https://ls.shron.de/dotconf | /bin/bash
After you've executed the setup, any file within the $HOME folder can be versioned with normal commands, replacing git with your newly created config alias, like:
config remote add dotconfs url.to.remote.repo
config checkout
config status
config add .vimrc
config commit -m "Add vimrc"
config add .bashrc
config commit -m "Add bashrc"
config push
Install your dotfiles onto a new system (or migrate to this setup)
config pull