yet another package and yet another config file and thus requires #Guix to support the target system.
@kkarhan well, that is not really how it works.
You write just one single Guix config, then Guix “derives” all the other config files for you. You don’t need to check-in the derived config files at all, because they are guaranteed to be derived the same exact way according to your one single master config file. Then you just check-in your single config file to a Git repo.
Also, all installed files are installed into their own separate store, so it never touches your actual /etc
or /usr
directories, this is how it can live safely side-by-side with any other operating system.
But I did not know you wanted to do this on a non-Linux system, so I can see how Guix is maybe not an option for you.
Can your operating system build the Guile Scheme programming language? If so, you can probably build Guix on your OS pretty easily.