Source: boost1.71 Followup-For: Bug #972213 X-Debbugs-Cc: debian-python@lists.debian.org
Would it make sense to use the Built-Using [1] header? e.g. Built-Using: python3.8 python3.9 dh_python3 knows if the module includes extensions (*_python*.so.) and could inject the pythons into Built-Using. dh_golang does something like this for the Go packages. There's a nuance which I don't fully understand about the intended use of Built-Using, which means it's not really the proper solution for the Go packages. I think that's related to the fact that Go applications are statically linked. The Python extensions are dynamically linked so maybe Built-Using could work fine. [1] https://www.debian.org/doc/debian-policy/ch-relationships.html#additional-source-packages-used-to-build-the-binary-built-using
