summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-stdnum
diff options
context:
space:
mode:
authorFlorian Klink <flokli@flokli.de>2019-05-08 12:03:26 +0200
committerFranz Pletz <fpletz@fnordicwalking.de>2019-05-24 18:33:28 +0000
commit32c25b4f1d09fcb08b9ef0a409243c3da5db1101 (patch)
treecb2025569b941e852867d64218d764abec382f42 /pkgs/development/python-modules/python-stdnum
parentf41618a7c3a568005319a71c2bb2bc4cb49fec97 (diff)
shairport-sync: set sysconfdir to /etc/
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.
Diffstat (limited to 'pkgs/development/python-modules/python-stdnum')
0 files changed, 0 insertions, 0 deletions