>> So, let's say we initially start with packages available
>> critpath, then we don't have to worry whether a package provides
>> any shared library or not.
> Let me try this another way. Let's assume we can detect whether a
> certain package contains an *.so (or *.so.N+) file. Can we use this to
> decide which packages to run libabigail on?
If by "we" you mean taskotron, then the answer to your question is yes.
> Or does libabigail run checks on more files than just *.so (now that
> we're using --dso-only)?
Now that the taskotron task is invoking abipkgdiff with the --dso-only
option, if the package contains shared libraries and and other types of
binaries, then only the shared libraries are going to be ABI-compared.
> I'm asking, because I expect this request ("run my task on packages
> containing shared libraries/files or certain other kind") is going to
> be quite common in the future and I think we should cover it somehow
> (and I have an idea how). I understand that currently we can run
> libabigail on everything, and if there are no libraries inside,
> nothing bad happens. But it's not very efficient, and that's why I'm
> interested to learn how exactly to distinguish packages libabigail is
> useful for from packages libabigail just skips.
I understand. I agree that being able to skip packages early based on
their content would likely be more efficent.
I hope this helps.
Thanks, I reported an RFE about this: