Andrew Cooper writes ("Re: Stable ABI checking (take 2)"): > It turns out that libxl causes abi-dumper to churn for ~4s or so, which > isn't ideal. All the other libraries are in the noise.
I think that means making it part of "make check" or something. > However, to fix problems pertaining to the unstable libraries, > downstreams do need to be able to invoke checking on the other libraries > as well. Fine by me. Ian