summaryrefslogtreecommitdiff
path: root/setup.cfg
diff options
context:
space:
mode:
authorChristian Schwede <christian.schwede@enovance.com>2014-01-20 10:55:20 +0000
committerChristian Schwede <christian.schwede@enovance.com>2014-01-20 11:24:16 +0000
commit65d7a136f69a2f0a692eeaed7ca68e2a5f91b07d (patch)
treedd2b83b4d7fd2873c78b3d2315d78b4ee16e18f6 /setup.cfg
parentb4907e0c816585d9b20a4119b00ee56adb884119 (diff)
downloadpython-swiftclient-65d7a136f69a2f0a692eeaed7ca68e2a5f91b07d.tar.gz
Install manpage in share/man/man1 instead of man/man1
According to FHS 2.3 the correct place to install the manpage for a binary in /usr/local/bin/ would be /usr/local/man/. However, on Debian/Ubuntu-based systems /usr/local/man/ is a link to /usr/local/share/man/ and on other systems /usr/local/man/ might not exist at all. Even worse, if the client is installed in /usr/bin/ the manpage should should be installed in /usr/share/man, but will be installed in /usr/man/ which is completely wrong. This patch fixes this and uses share/man/man1 as common prefix. Doing this will install the manpage either in /usr/local/share/man/man1 or /usr/share/man/man1. Partial-Bug: 1269715 Change-Id: I590932f00476eacd434cdae012fd62010845581d
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 6947f06..a7f8c2d 100644
--- a/setup.cfg
+++ b/setup.cfg
@@ -27,7 +27,7 @@ packages =
scripts =
bin/swift
data_files =
- man/man1 = doc/manpages/swift.1
+ share/man/man1 = doc/manpages/swift.1
[build_sphinx]
source-dir = doc/source