summaryrefslogtreecommitdiff
path: root/setup.cfg
diff options
context:
space:
mode:
authorSascha Peilicke <saschpe@gmx.de>2014-02-07 12:29:01 +0100
committerSascha Peilicke <saschpe@gmx.de>2014-02-07 12:29:35 +0100
commit4e70ff2e6204f74767c5cab13f118d72c2594760 (patch)
tree29092724de66592ad9028717ef290f595bc146a0 /setup.cfg
parenta4fbcc87f00104753d4f46aacc13d3a6688d2e1b (diff)
downloadpycadf-4e70ff2e6204f74767c5cab13f118d72c2594760.tar.gz
Install configs into /etc, not /usr/etc
Not providing an absolute path to data_files means that "setup.py install" will put it under whatever "--prefix" is specified. For most RPM-based distros this is /usr. For machine-local installations this is /usr/local. However, there's no such thing as /usr/etc or /usr/local/etc, there's just /etc. Distributions could either fix this manuall or work-around by using "python setup.py --install-data=/etc". But this isn't future-proof since all data would end up in the (potentially) wrong place. Change-Id: I844b33d1fdd87f2c255f72b30a78eeab677ec09d
Diffstat (limited to 'setup.cfg')
-rw-r--r--setup.cfg2
1 files changed, 1 insertions, 1 deletions
diff --git a/setup.cfg b/setup.cfg
index ea5da43..ab1c8a0 100644
--- a/setup.cfg
+++ b/setup.cfg
@@ -22,7 +22,7 @@ classifier =
packages =
pycadf
data_files =
- etc/pycadf =
+ /etc/pycadf =
etc/pycadf/api_audit_map.conf
[global]