New comment by freshprince on void-packages repository

https://github.com/void-linux/void-packages/pull/34676#issuecomment-1002971905

Comment:
> Was curious what benefit directly execing logger has? I have this running on my system and synapse is already logging to daemon.notice.

I was used to see error output in the logging space of `runsvdir`, when I saw that there was a logging service running for synapse there was no easy way for me to see where it is logging to. All other services I use do have explicitly set where they are logging to and in this case explicit is better than implicit because if you want to check logs you shouldn't need to know what's the default behaviour of vlogger.

> For patching config files, I'd like to have the config file updates installed so that e.g. xdiff from xtools can be used to easily manage updates/changes to the synapse configuration. Currently that's waiting on void-linux/xbps#426, then hopefully we can install to /etc/synapse instead of vsconf.

If you read the [first three paragraphs of the config file that you want to install](https://github.com/matrix-org/synapse/blob/develop/docs/sample_config.yaml) you see that this config file is not intended to be copied into `/etc/synapse`, patched or otherwise. The config does contain several secrets that should be randomly generated and for this the correct and documented way is to use `generate_config`. Regardless of the behaviour of xbps that resulted in https://github.com/void-linux/xbps/issues/441.

Please test your patches before you create pull requests.