Honestly, I was running into the limits of stow. Want to unstow some configs on a bare machine? I hope you wanted that entire directory to be a symlink. Then I saw that someone had actually fixed that many years ago but the maintainer at the time was caught up in some personal crypto related projects and did not appear to be looking at the mailing list.

Chezmoi fixed that, applied a templating engine and added a data mechanism. In moving my stow configs I realized that application specific config file deployments are nice but shouldn’t be necessary. Templates fill that gap, and meshing them with scripts allows you to do some cool things only when variables change.

Plus I was beginning to play around with go at the time, so it just seemed like a good idea to use something I could contribute to if I needed.

I still don’t think I’m using chezmoi to it’s full potential, but I am fairly proud of the script I use to determine data sources for my waybar config on all of my machines.

All public and I regularly link people to my bash functions. Started with git bare repos, moved to stow, now on chezmoi. If I need anything more complex than chezmoi for these I’ll probably give up syncing them altogether.

https://github.com/StaticRocket/dotfiles

It’s astounding how many lowlifes are using commit counts to measure impact. It’s just throwing bisectability out the window and promoting stupid tactics for quick returns.

I use them all the time, but that’s just because of Yocto and the need to keep at least the 3 major LTS builds hot in the event something breaks.

The problem here being these payment processors are global and none of this is illegal in the jurisdictions affected. This regional blocking, while nice, shouldn’t even need to be a “solution” to this. It’s a sledgehammer “solution” to something that was never enough of an issue for actual legislation.

Edit: clarify point