Package: dh-builtusing
Followup-For: Bug #1052427
Hello.
The motivation for
Built-Using: ${dh-builtusing:gcc-S-source}
is that the maintainer wants everyone else to be able to replace
Build-Depends: gcc-13-source
with
Build-Depends: gcc-14-source
and rebuild the package.
The purpose of dh-builtusing is to generate the version of each
package, but I fear that computing (part of) the package list may
easily lead to false positives. For example a source may start
building several rust libraries with distinct new build dependencies.
Also, the benefice is low because a change (not restricted to
versions) in the list of Build-Depends is rare and probably already
involves decisions by the maintainer anyway.
Also, should
Built-Using: ${dh-builtusing:librust-WILDCARD-dev} [amd64] <nodoc>
be forbidden?
The only logic expansion is
Built-Using: librust-a-dev [amd64] <nodoc>, librust-b-dev [amd64] <nodoc>
This can be implemented, but would be inconsistent and probably fragile.
Same question for ${dh-builtusing:librust-WILDCARD-dev:amd64}.
