Open Stack

It turns out that oslo-config and Debian packaging create at least a little bit of a mess, as I've discovered when attempting to do so. 

Packages depending on oslo-config will depend on 'oslo.config' in their setup.py. Debian packaging will, at least by default, map this to 'python-oslo.config'.  However, the sdist tarball and the directory said tarball creates are, well, "oslo-config", not "oslo.config". This means that the packages we create for 'oslo-config' will be called 'python-oslo-config'.  To clarify and reiterate, this means packages will depend on 'python-oslo.config', but the package will actually be called 'python-oslo-config'.

Even if we had a workaround for the consuming projects to put into their individual setup.py scripts, this would be quite onerous to presume of projects that simply want to use a module.  One solution that pleases debuild is to do setuptools.setup(name='oslo.config'), although I don't think this is a good Pythonism and might anger the PyPi gods.

I'm far from being a subject-matter-expert in either setuptools/distribute or Debian packaging, so I'd like to get community feedback and opinions on what the  options and path forward is here. Also, if I'm personally doing something wrong, I'd love to know it. 

Regards,
Eric Windisch