Package: sphinx-common Version: 1.4.6-1 Severity: normal File: /usr/bin/dh_sphinxdoc
Dear maintainer, If a package installs sphinx documentation then it can embed code from sphinx themes, such as python3-alabaster. That means it needs a "Built-Using: python3-alabaster (= foo)". dh_sphinxdoc could provide a substvar for this purpose. I selected severity 'normal' rather than 'wishlist' since without such a substvar packages using sphinx themes are violating policy. It is not really feasible to supply Built-Using without a substvar as then a exactly-equal build dependency on the sphinx theme in question would be required. (Is there some reason why the copy of the theme is not turned into symlinks by dh_sphinxdoc, as embedded javascript is?) Thanks. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Kernel: Linux 4.5.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sphinx-common depends on: ii libjs-sphinxdoc 1.4.6-1 Versions of packages sphinx-common recommends: ii python3-sphinx 1.4.6-1 sphinx-common suggests no packages. -- no debconf information -- Sean Whitton
signature.asc
Description: PGP signature
_______________________________________________ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
