Just like writing and qutebrowser modules, restructured the version
control software module to make more use of dotter's ability to
precisely link files. All contained programs have a top-level directory
and all the files that correspond to that specific software lie beneath
in the directory tree.
Similarly to the qutebrowser module we change the layout to have a
program name at the top-level and all required files for that specific
program within, whether they reside within .config, .local or anywhere
else.
We use dotter mappings to achieve this.
Since we have extracted changes into private repository, change the files
containing them into templates so they do not get overwritten by branch
changes.
Moved usernames and passwords into local variables in dotter
to be able to commit the files nonetheless. Thus makes use
of dotter templating for beets and mopidy.
Empty example configuration can be found in local.toml in the
dotter directory.
Since sioyek does not support including into its configuration
file, we switch it to dotter templating and use the in-place
flavours insertion on theme selection for theming.
Any theming will not back filter into the repository.
Fixed an accidentally templated (papistui.yml) file, due to its
use of mustache-like double-braces.
Explicitly target another file as templated so we can change it
in the configuration directory (mako getting flavours colors
since it STILL lacks includes).
Fix the warnings given by dotter for files that are not
utf-8 encoded to explicitly be identified as symlinks.
Should ultimately probably be either moved into data
directories or moved out of repo altogether, but for
now it works well.
Since we now use dotter we can simplify the dir structure for
qutebrowser a lot. Everything dot-filed earlier can now reside
in simple directories called config (for ~/.config/qutebrowser),
data (for ~/.local/share/qutebrowser), and scripts
(for ~/.local/bin) files.
Everything that is in the repo should be listed in the global.toml
file. The local.toml file then picks the stuff to actually
write. For systemwide packages, a systemwide.toml (local) file
is used instead.
