#1115882 please let's make the *.ali checksum a bit more useful

#1115882#5
Date:
2025-09-21 05:58:37 UTC
From:
To:
with the recent ABI change, it was non-obvious, which "ABI" part
changed, so I would like to propose to provide a little bit more of
information, where the ABI is changing.

Please consider shipping one file together with the .ali files, e.g.
ali-checksums.xz, which lists per line
<name of ali file>  <xor'ed checksums from that file>

and then calculate the gnat checksum from that file.  That way, it's
easier to get a hint on what maybe is causing an ABI change for the gnat
checksum.

#1115882#10
Date:
2026-02-27 22:58:24 UTC
From:
To:
Hello.

I once had the same problem and spent a hard time comparing the old
and new .ali files.
The solution was to forget them once they have played their role of
alert, and compare the sources directories with something like 'diff
-urN'.
When we search for an unexpected ALI breakage, the changes are
unexpected, hence usually quite small.