Hello,
Ray Kinsella <m...@ashroe.eu> writes:
> ah ok, the particular system I made the change on was Ubuntu 18.04.2.
> which is libabigail 1.2.0.
Whoah, 1.2 is super old.
In my opinion, one of the hallmarks of static analysis tools (and
libabigail is just a static analysis framework) is to be able to
recognize patterns used by developers, as much as we can.
Because we can't really do that at once, we try to add recognition of
new patterns (of ABI changes) at every single release. Furthermore,
there are some change patterns that ought to be recognized and
categorized as harmless, whereas some others out to be categorized as
harmful. That categorization is also the result of input coming from
users as you, fine fellows.
All this to say that with every new version, the number of new supported
features and bug fixes is potentially big.
To alleviate that, some distributors update libabigail even in their old
stable distros, because the value of having an up to date version there
outweighs the potential drawbacks.
> Given we still support v19.11 on Ubuntu 18.04.2.
So maybe that's a discussion worth having with the maintainer of the
Ubuntu package of Libabigail?
> I think it's worthwhile keeping the suppression until v20.11?
[...]
David Marchand <david.march...@redhat.com> writes:
> In Travis, we currently use libabigail 1.6 (mainly because I did not
> update to 1.7 when it was released).
Right, that's probably another way to stay up to date independently from
the underlying distribution.
I hope this helps,
Cheers,
--
Dodji
