Ah, typical: while trying to figure out where functionality like this could fit into Debian, I learned that it already exists there.
The 'dpkg-depcheck' and 'dpkg-genbuilddeps' utilities (both included in the 'devscripts' package) provide this kind of functionality in Debian. On Wed, 14 Dec 2022 at 00:38, James Addison <j...@jp-hosting.net> wrote: > > On Tue, 13 Dec 2022 at 18:15, Vagrant Cascadian > <vagr...@reproducible-builds.org> wrote: > > > > It would be interesting to do something more systematic like your > > suggestion, though I'm not aware of anything at the moment. > > Thanks Vagrant, that's good to know (it matches my understanding too, > from searching around). > > Roughly speaking, the reason I ask is to see whether it'd be possible > to reduce migration and maintenance burden (in terms of maintainer > time, primarily, although perhaps arguably also compute resources) by > providing information about no-longer-required build dependencies. > > I'll spend some time at the metaphorical drawing board to see whether > something like this could make sense and how to integrate in a > non-disruptive way if so. > > James