"meson install" tries to install an example config with a default service key

[delroth]

When running "meson install", the build system installs example.cfg as the default configuration. Since example.cfg is a working config file with a hardcoded key, this seems like a dangerous behavior.

Luckily, it happens that a bug makes this harmless right now: meson installs to ${sysconfdir}/config while glome-login attempts to look up the config in ${sysconfdir}/glome/config. I suspect this is however not deliberate :-)

[pkern]

The latter is addressed by #36. #28 talks about improving the whole config setup.