Bug 10950

Summary:	Allow binaries to be shared along with some compatibility metadata
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Stephano Cetola <stephano>
Component:	core	Assignee:	Unassigned <unassigned>
Status:	RESOLVED OBSOLETE	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	joshuagloe, meta.mr.watcher, meta.watcher, randy.macleod, richard.purdie
Version:	2.2
Target Milestone:	Future
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know
Bug Depends on:
Bug Blocks:	10664

Description Stephano Cetola 2017-01-20 20:22:33 UTC

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.

Comment 1 Stephano Cetola 2017-01-20 20:25:20 UTC

*** Bug 10663 has been marked as a duplicate of this bug. ***

Comment 2 Stephano Cetola 2017-08-10 18:07:51 UTC

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.

Comment 3 Richard Purdie 2022-06-30 15:09:00 UTC

Not sure we need/want to do this now.