On 09/01/2017 10:00 AM, Igor Gnatenko wrote: > On Fri, 2017-09-01 at 09:28 -0500, Carlos O'Donell wrote: >> Fedora Developers, > >> I am working on a way to provide concrete ABI/API assurances for >> parts of the base runtime. > Note that Base Runtime is F26-only thing and in F27 it is called Host > and Platform[0].. Thanks! I've updated the proposal based on the new split of host, platform, and bootstrap. >> I've written up some of the key ideas here: >> https://fedoraproject.org/wiki/BaseRuntimeInterface > >> Any feedback would be appreciated, including bikeshed on component >> name prefix for frozen interface pakcages e.g. base-*. > Why do we need separate components? Can't we adjust main packages to > install into separate paths? In theory, it should be just setting > differeng %_prefix variable for RPM. I have added a "Questions" section to address this. There are two reasons to split the packages completely: * Reduce validation cost for each build e.g. build and validate the interface fewer times. * Reduce storage costs e.g. build the interface only once for each important transition point including package rebase. > Another thing to mention is that libabigail currently (as far as I > know) doesn't handle python code/python extensions (read DNF). Also I > guess it doesn't handle GObject Introspected code. Correct, Python and any code that does dynamic introspection (which causes cross-compilation problems) are currently out of scope for such separation. libabigail can only look at the binary artifacts (DSOs) which would be generated from a Python build and characterize those. In the case of GObject code, I already knew that we could not support such separation with that kind of code. Effectively what I am suggesting is a small amount of cross-compilation compatibility with the low-level runtimes in order that we can upgrade them if required in the Platform module. Does that answer your questions? -- Cheers, Carlos. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
