since 2.8.5, shairport-sync uses the directory path sysconfdir to
determine where to place the configuration file shairport-sync.conf.
This led to shairport-sync complaining at startup:
> configuration file name "/nix/store/i8gb0hsb2zczdl8g1h73pbcb952585l9-shairport-sync-3.2.2/etc/shairport-sync.conf" can not be resolved.
Looking for a configuration file there doesn't make much sense, as we'd
have to include configuration in the shairport-sync derivation itself.
By setting sysconfdir to /etc/, shairport-sync will try to read its
configuration from /etc/shairport-sync.conf, which is a more sane
default.
Semi-automatic update. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 3.1.7 with grep in /nix/store/8r3k0r8vf0wfpj14443pm1k0jddlnii2-shairport-sync-3.1.7
- found 3.1.7 in filename of file in /nix/store/8r3k0r8vf0wfpj14443pm1k0jddlnii2-shairport-sync-3.1.7
- Enable additional backends: pipe, stdout
- Support high-quality resampling with soxr
- Support configuration files, but don't install one
- Cut down on boilerplate code with fetchFromGitHub/autoreconfHook
