|
A different view worth considering: Dotfiles are just a component, but not the whole story, of your personal compute environment. Your environment also includes things like: * ~/bin scripts (etc) * programming language stuff - e.g. go, rust, python, ruby etc have tooling for per-user package management, language version, etc. * various forms of password/key/auth stuff like ssh allow lists, encrypted password stores, etc. And the biggest one: Type of machine - work, daily driver, server, etc The type of machine may require different dotfiles or different parts of dotfiles (e.g. what basrc includes from `. .config/bash/my_local_funcs`), and having some scripting around this makes life easier. Similarly OS packages are great, and I use them heavily, but work and personal servers and personal desktop all use a different OS, so its useful to have provision scripts for the type of machine, and i keep all that together with my dotfiles (etc) in my "personal environment repo" (it's name is dots, and when i talk about dotfiles I really mean "personal environment". I suspect other share this view, which leads to this "pure dotfiles" vs "dotfiles+parts of provisioning" viewpoint difference even though they largely have the same set of problems and tooling. |