This was causing the setup.py to try to install the files listed
For example:
running install_data
copying LICENSE.txt -> /builddir/build/BUILDROOT/python-pyvmomi-5.5.0.2014.1.1-1.fc20.x86_64/usr/
copying NOTICE.txt -> /builddir/build/BUILDROOT/python-pyvmomi-5.5.0.2014.1.1-1.fc20.x86_64/usr/
copying MANIFEST.in -> /builddir/build/BUILDROOT/python-pyvmomi-5.5.0.2014.1.1-1.fc20.x86_64/usr/
copying setup.py -> /builddir/build/BUILDROOT/python-pyvmomi-5.5.0.2014.1.1-1.fc20.x86_64/usr/
copying tox.ini -> /builddir/build/BUILDROOT/python-pyvmomi-5.5.0.2014.1.1-1.fc20.x86_64/usr/
copying setup.cfg -> /builddir/build/BUILDROOT/python-pyvmomi-5.5.0.2014.1.1-1.fc20.x86_64/usr/
Those files should not go in that location.
The MANIFEST.in file does enough by adding those files to the sdist
from there if you intend to have those files installed by setup.py
you should tell it where to put them. This change allows packagers
to specify where those files end up in their packaging process.
Changes version standard to use `-` character when available.
By convention `-` is translated to `.` from now on when the
`-` character is prohibited by downstream systems.
Closes: https://github.com/vmware/pyvmomi/issues/127
All development versions should be marked with yyyy.dev to denote that they are unstable development versions. Release versions will be marked 5.5.0_2014.1 (release 1) and so on with whole integer release numbers after the year.
This is the initial version of pyVmomi which represents vSphere API 5.1.
Going forward, expect only the 'Objects' and 'Types' generated source
files to need updating via official OSS drops.
