Hi,
On Fri, 22 Sep 2023 19:51:39 +0200 Nicolas Boulenguez
<nico...@debian.org> wrote:
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.
I’m afraid this is exactly the argument for the inclusion of this
feature, as otherwise two lists with slightly different syntax need to
be maintained by hand, which is really easy to get wrong, especially
e.g. when doing backports and cherry-picking changes between branches.
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}.
Well, this would be no different to ${perl:Depends} and other variables
expanding to a list: this would be a responsibility of the maintainer to
ensure the syntax of debian/control is valid and doesn’t cause incorrect
expansions.
--
Cheers,
Andrej
