Path: csiph.com!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!news.dns-netz.com!news.freedyn.net!aioe.org!bofh.it!news.nic.it!robomod From: Drew Parsons Newsgroups: linux.debian.bugs.dist,linux.debian.maint.python Subject: Bug#972213: boost1.71: Please indicate some way which python versions you support Date: Fri, 16 Oct 2020 03:00:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Fri Oct 16 00:57:08 2020 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: -4.2 Reply-To: Drew Parsons , 972213@bugs.debian.org Resent-To: debian-bugs-dist@lists.debian.org Resent-Cc: debian-python@lists.debian.org, Debian Boost Team X-Debian-Pr-Message: followup 972213 X-Debian-Pr-Package: boost1.71 X-Debian-Pr-Source: boost1.71 X-Spam-Bayes: score:0.0000 Tokens: new, 17; hammy, 133; neutral, 45; spammy, 0. spammytokens: hammytokens:0.000-+--followupfor, 0.000-+--followup-for, 0.000-+--FollowupFor, 0.000-+--Followup-For, 0.000-+--debianpolicy X-Originating-IP: 203.59.251.67 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Mailer: reportbug 7.7.0 X-Debian-Message: from BTS X-Mailing-List: archive/latest/1627553 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 20 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Fri, 16 Oct 2020 08:53:02 +0800 X-Original-Message-ID: <160280958293.174864.15697454085967198930.reportbug@monte.emerall.com> X-Original-References: <160268352629.28072.10388202521171168675.reportbug@mail.sceal.ie> Xref: csiph.com linux.debian.bugs.dist:1028793 linux.debian.maint.python:12942 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