delta/openstack/python-swiftclient.git/setup.cfg, branch 2.0.3 opendev.org: openstack/python-swiftclient.git Install manpage in share/man/man1 instead of man/man1 2014-01-20T11:24:16+00:00 Christian Schwede christian.schwede@enovance.com 2014-01-20T10:55:20+00:00 65d7a136f69a2f0a692eeaed7ca68e2a5f91b07d 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 
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
Install swiftclient manpage 2014-01-16T10:26:06+00:00 Christian Schwede christian.schwede@enovance.com 2014-01-16T10:23:02+00:00 63c9917085ac4d5c99afc61e5865cb88417dcd27 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 
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
Switch to pbr for setup. 2013-05-01T16:23:12+00:00 Monty Taylor mordred@inaugust.com 2013-04-29T02:46:03+00:00 50f32bc803b42a33533af1ce379da930ddd8f494 Change-Id: Ifc2efa2bd7c2f030b51494ccb471f0c3e097c5ce 
Change-Id: Ifc2efa2bd7c2f030b51494ccb471f0c3e097c5ce
Use testr instead of nose. 2013-01-18T21:13:27+00:00 Monty Taylor mordred@inaugust.com 2012-12-27T23:26:50+00:00 bfeffb63667b796999997acf43be395d31b6a184 nose is invasive and can sometimes alter the outcome of a test run. testr, on the other hand, keeps a distinction between running tests and displaying results of the test runs. Additionally, it supports the stock python unittest protocol. Even better, testr supports parallel test running, which makes things faster, and a command "testr run --failing" which will just re-run the latest failing tests (often something one wants to do in iterative dev) Part of blueprint grizzly-testtools Change-Id: I0b3f1bcb5d4ff59c65eb3219b30a9e64f54d70bd 
nose is invasive and can sometimes alter the outcome of a test run. testr,
on the other hand, keeps a distinction between running tests and displaying
results of the test runs. Additionally, it supports the stock python unittest
protocol.

Even better, testr supports parallel test running, which makes things faster,
and a command "testr run --failing" which will just re-run the latest failing
tests (often something one wants to do in iterative dev)

Part of blueprint grizzly-testtools

Change-Id: I0b3f1bcb5d4ff59c65eb3219b30a9e64f54d70bd
tell nose to explicity test the 'tests' directory 2012-11-08T15:55:15+00:00 John Dickinson me@not.mn 2012-11-07T16:40:49+00:00 b4272711ed3591ffff1c7c301201e7b5dbbd815a Change-Id: Ib6afa775defc521794da627952edbf69721b0874 
Change-Id: Ib6afa775defc521794da627952edbf69721b0874
Add build_sphinx options. 2012-06-11T21:51:40+00:00 Clark Boylan clark.boylan@gmail.com 2012-06-11T21:50:21+00:00 12519ce0266875e6644399a25156c1b8691248ef 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 
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
Added setup.cfg for verbose test output. 2012-05-21T13:09:13+00:00 Monty Taylor mordred@inaugust.com 2012-05-21T13:09:13+00:00 bee9ae504270c6cd73663ba1a6f63c32fc66850a