tempest/setup.cfg
Andrea Frittoli (andreaf) 871f5daa04 Use relative path in data_files in setup.cfg
The absolute path causes failures when installing in a virtual
environment, not having root privileges.

This change solves the installation in a virtual environment,
but it does not fix yet the tempest init workflow when installing
into a virtual environment.

Partially-fixes bug #1480389

Change-Id: Iddefb8db77ffe35a84fb35b6f9e7e823de4ab45f
2015-07-31 17:55:38 +01:00

47 lines
1.2 KiB
INI

[metadata]
name = tempest
summary = OpenStack Integration Testing
description-file =
README.rst
author = OpenStack
author-email = openstack-dev@lists.openstack.org
home-page = http://www.openstack.org/
classifier =
Intended Audience :: Information Technology
Intended Audience :: System Administrators
Intended Audience :: Developers
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 :: 3
Programming Language :: Python :: 3.4
[files]
packages =
tempest
data_files =
etc/tempest = etc/*
[entry_points]
console_scripts =
verify-tempest-config = tempest.cmd.verify_tempest_config:main
javelin2 = tempest.cmd.javelin:main
run-tempest-stress = tempest.cmd.run_stress:main
tempest-cleanup = tempest.cmd.cleanup:main
tempest-account-generator = tempest.cmd.account_generator:main
tempest = tempest.cmd.main:main
tempest.cm =
init = tempest.cmd.init:TempestInit
oslo.config.opts =
tempest.config = tempest.config:list_opts
[build_sphinx]
all_files = 1
build-dir = doc/build
source-dir = doc/source
[wheel]
universal = 1