Re: ABI Compliance Checker GSoC Project

On Mon, 14 Jul 2025 at 00:32, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Another idea could be an in-tree file, different in each branch,
> that records the hash of the commit we presently want to compare to.
> This would require a small amount of additional manual effort to
> maintain, but maybe it's the most flexible way.  Notably, we could
> say that if the file isn't present in a given branch then we don't
> want any ABI checking, whereas with the tag approach I think we'd
> need some hard-coded rule about which branches to ignore.

In-tree file seems fair as buildfarm clients already use them for operations.
Additionally, the abidiff tool provides its own way to suppress
specific symbols in the reports [1], which, as you mentioned, would
rarely be required for stable branches. Beta branches could be handled
similarly, and this will also not require us to maintain the record of
commits for individual branches; a single suppression file might work
for all branches. Hence, we can directly use the most recent tag as
discussed earlier.

Regards,
Mankirat

[1] - https://sourceware.org/libabigail/manual/suppression-specifications.html