Currently, if I want to share a binary package created in Yocto, my best bet is something like package_tar. If the group consuming the binary is also using Yocto, it would be nice to be able to check for compatibility. We could generate a manifest file containing details of how the package was built. That file could then be parsed by the consumer in order to do some basic checks for compatibility. Sharing details like CC, LDFLAGS, distro config, or preferred versions could be helpful. It might also be helpful to define a "vanilla Yocto environment" which could be used to ensure compatibility for the consumer. The list of possible customizations to the build environment is obviously quite large, so any input here is welcomed.
*** Bug 10663 has been marked as a duplicate of this bug. ***
I believe our best bet is to use libabigail for this task: https://sourceware.org/libabigail/manual/index.html Binaries can be cached and compared with later versions, much like with packagefeed-stability.
Not sure we need/want to do this now.