I take those to be a yes to wanting this option to *exist*, though if it
already exists in rebuilderd then it might make more sense to use that.
(It would probably also make sense to use rebuilderd instead of
reprotest on Salsa to save resources, i.e. requiring 1 extra build
instead of 2.)
Helmut Grohne wrote:
> Reproducibility likely degrades in even more cases
as the compiler flags may change and they influence the buildid.
Chris Lamb wrote:
> Many many packages generate stuff during test runs which then gets
installed into a binary package.
If either of these turn out to be very common, it might make more sense
to change the policy from "nocheck must not change anything at all in
the binary packages" to "nocheck must not remove any functionality from
the binary packages (including testing tools - use noinsttest for
that)", but we probably want to gather more data before actually deciding.
