Generating abi reports inside chroot solves the problem of unclean abi reports when packagers do not have all dependencies installed.
This requires that abi-wizard be packaged as part of the system.develcomponent to ensure it is always available inside of the chroot.
Notes:
Given continued ypkg3 work merging this is not a requirement, however, if development of that is stalled I would recommend this to get merged in the meanwhile. I have opened this PR as it is useful to me and may be useful to others.
It should be possible to use the abi-wizard API instead of calling the binary, that would also avoid the requirement of havingabi-wizard in system.devel. However, my smol brain wasn't able to figure out how to get that working using the available helper - chrootExec.
Generating abi reports inside chroot solves the problem of unclean abi reports when packagers do not have all dependencies installed.
This requires that
abi-wizardbe packaged as part of thesystem.develcomponent to ensure it is always available inside of the chroot.Notes:
abi-wizardinsystem.devel. However, my smol brain wasn't able to figure out how to get that working using the available helper -chrootExec.