Install scripts in /usr/bin with extensions

[Thomas Goirand]

It's generally forbidden in distributions (like Debian or RedHat) to install scripts in /usr/bin with the scripting language extension. Here's the errors from the Debian lintian tool:

W: barbican-common: script-with-language-extension usr/bin/barbican-db-manage.py
N:
N: When scripts are installed into a directory in the system PATH, the
N: script name should not include an extension such as .sh or .pl that
N: denotes the scripting language currently used to implement it. The
N: implementation language may change; if it does, leaving the name the
N: same would be confusing and changing it would be disruptive.
N:
N: Refer to Debian Policy Manual section 10.4 (Scripts) for details.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: files, Type: binary, udeb
N:
W: barbican-common: script-with-language-extension usr/bin/barbican-keystone-listener.py
W: barbican-common: script-with-language-extension usr/bin/barbican-worker.py
W: barbican-common: script-with-language-extension usr/bin/barbican.sh

Please fix this.

[Thomas Goirand (thomas-goirand)]

Oh as well... this kind of things should be handled by PBR entry points, not manually creating a script in bin/*. Please have a look into other projects on how they do it.

[Douglas Mendizábal (dougmendizabal)]

I've read about removing the language extension from executable scripts, since it should not necessary to know what language they're written in when you execute them.

Entry points are a feature of setuptools [1] not PBR. It would definitely be interesting to move this script into the code tree and provide an entry point for it.

[1] http://pythonhosted.org//setuptools/pkg_resources.html#entry-points

[Thomas Goirand (thomas-goirand)]

Hi. I know it's from setuptools, however it's even more easy to use with PBR... :)