openstack/python-swiftclient
Code Issues Proposed changes
cdf6f84c36
python-swiftclient/setup.cfg

41 lines
951 B
INI
Raw Normal View History

Switch to pbr for setup. Change-Id: Ifc2efa2bd7c2f030b51494ccb471f0c3e097c5ce
2013-04-28 19:46:03 -07:00
[metadata]
name = python-swiftclient
summary = OpenStack Object Storage API Client Library
description-file =
README.rst
author = OpenStack
author-email = openstack-dev@lists.openstack.org
home-page = http://www.openstack.org/
classifier =
Environment :: OpenStack
Intended Audience :: Information Technology
Intended Audience :: System Administrators
License :: OSI Approved :: Apache Software License
Operating System :: POSIX :: Linux
Programming Language :: Python
Programming Language :: Python :: 2
Programming Language :: Python :: 2.7
Programming Language :: Python :: 2.6
[global]
setup-hooks =
pbr.hooks.setup_hook
[files]
packages =
swiftclient
Install swiftclient manpage Currently the existing manpage isn't copied to /usr/local/man/man1 when installing swiftclient from source. This patch fixes this. Change-Id: Ib2ee091d5e1d4c37a4e5a00f50fa19df44bd3c41 Partial-Bug: 1269715
2014-01-16 10:23:02 +00:00
data_files =
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
2014-01-20 10:55:20 +00:00
share/man/man1 = doc/manpages/swift.1
Switch to pbr for setup. Change-Id: Ifc2efa2bd7c2f030b51494ccb471f0c3e097c5ce
2013-04-28 19:46:03 -07:00
Make bin/swift testable part 1 To make bin/swift importable for testing it needs to be renamed/moved. The final idea is to move it to swiftclient/shell.py and add only a stub in bin/swift to import swiftclient/shell.py. However, doing this in a single step makes reviewing very hard, because now there are > 1400 lines deleted from bin/swift and added to swiftclient/shell.py - Gerrit doesn't detect the moved file. For example: https://review.openstack.org/#/c/73710/2/ This patch first moves the code to swiftclient/shell.py and uses setup.py/cfg to create the stub file in bin/swift. A follow up (https://review.openstack.org/#/c/76489/) will then add the stub itself in bin/swift (and remove the entry in setup.py). The change to tox.ini is related to bug 1290562 and can be removed in the future. Change-Id: Id86392ccaf09e1d80a5d808fb49827d6d18c2588
2014-02-26 09:52:38 +00:00
[entry_points]
console_scripts =
swift = swiftclient.shell:main
Add build_sphinx options. To better facilitate the building and publishing of sphinx documentation by Jenkins we are moving all openstack projects with sphinx documentation to a common doc tree structure. Documentation goes in project/doc/source and build results go in project/doc/build. Change-Id: Ibe6745cac73817ea06faca77367b4269d5137a24
2012-06-11 14:50:21 -07:00
[build_sphinx]
source-dir = doc/source
build-dir = doc/build
all_files = 1
[upload_sphinx]
upload-dir = doc/build/html
Copy Permalink