Package: src:python-coverage Version: 3.4-3 Severity: normal The Python setup program for Coverage treats the static resources for HTML reports (the files in ‘coverage/htmlfiles/’) as “package data”, to be installed alongside the Python package.
This is a violation of FHS 2.3, §4. The Python libraries are installed to ‘/usr/lib/’ which is for “libraries for programming and packages”; but the report resources are treated by the package as “architecture-independent data”, so belong in ‘/usr/share/’. <URL:http://www.pathname.com/fhs/pub/fhs-2.3.html> Debian Policy §8.2 agrees that these architecture-independent data files should be in ‘/usr/share/’, preferably ‘/usr/share/<packagename>/’ (where “<packagename>” is the name of the binary package). Currently the Python code expects the report resources to be found as “package data” directly alongside the Python modules (on Debian, this is ‘/usr/lib/python<version>/dist-packages/coverage/…’). This access will need to change in the Python code, so the data files are sought in a separate version-independent location. Ideally this would be done using existing Python packaging and resource-access functions, to allow the change to be submitted upstream. -- \ “A free press is one where it's okay to state the conclusion | `\ you're led to by the evidence.” —Bill Moyers | _o__) | Ben Finney <b...@benfinney.id.au>
signature.asc
Description: Digital signature
