Hello, On Fri 05 Apr 2024 at 11:30am +02, Christian Kastner wrote:
> Hi again, > > On 2024-03-29 20:30, Christian Kastner wrote: >> Policy 5.6.30 lists the Testsuite field, but it doesn't list the >> Testsuite-Triggers field that seems to be part of Sources files and is >> generated by dpkg-source >= 1.18.8. >> >> This field is quite useful, as given my package src:foo, I can find out >> which packages have autopkgtests that depend on it, and are thus in the >> set of reverse dependencies that I could check for breakage. > > I've read up on the change process [1], and I guess my proposal to > submit a patch was too far into the process. > > Thus, I take a step back, and seek discussion first. > > In addition to what I've said above, I think documenting this field > would not only enhance discoverability, but give more weight to it for > tooling that makes use of these fields. > > For discussion context, I'd like to quote dsc(5) on this field: >> Testsuite-Triggers: package-list >> >> This field declares the comma-separated union of all test dependencies >> (Depends fields in debian/tests/control file), with all restrictions >> removed, and OR dependencies flattened (that is, converted to separate AND >> relationships), except for binaries generated by this source package and its >> meta-dependency equivalent @. >> >> Rationale: this field is needed because otherwise to be able to get the test >> dependencies, each source package would need to be unpacked. Sounds good to me. If you'd like to propose wording, there's some more guidance in our README.md. Thanks! -- Sean Whitton
signature.asc
Description: PGP signature
