There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages how-much-log-would-a-woodchuck-chuck-if-a-woodchuck-could-chuck-log
https://github.com/void-linux/void-packages/pull/42026

[RFC] common/environment/setup/install.sh: always add log service
- common/environment/setup/install.sh: always add log service
    - overridable by having a log service at `$pkgname/files/$service/log`
    - uses a sane default run script with the service name set as tag and daemon facility
    - warns if stderr is not redirected in the main service
    - example of warnings:
```
=> soju-0.5.2_1: running post_install ...
=> WARNING: soju-0.5.2_1: vsv: service 'soju' does not contain 'exec 2>&1' to log stderr
=> WARNING: soju-0.5.2_1: vsv: overriding default log service
```
- Manual.md: document vsv log autocreation
- *: remove log dir en-masse

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

### TODO
- [ ] go through all removed log services and see if any need overrides
    - candidates at a glance: cronie, dcron, dkimproxy, dnscrypt-proxy, dq, postgres13/14, sqmail
- [ ] add/fix redirection to main run file of all services

### Questions
- Should there be a possible second vlogger argument that sets the facility? This would remove the need for overrides for the few services that set cron/mail as facility

[ci skip]

A patch file from https://github.com/void-linux/void-packages/pull/42026.patch is attached