Ian Stakenvicius wrote: > > Is it unrealistic to assume that upstream ABI providers will mark > > their ABIs by using sonames correctly? > > > > Maybe that is at least the common case, then ABI_SLOT could be set > > automatically. > > Although we have a lot of this information available (which is why/how > @preserved-libs works, for instance), there is no way for portage to > know *prior to emerging the update* if abi has changed.
Knowing that a library changes ABI before building is nice, but not relying on a human to encode this is nicer still. After compile, before install, there is an opportunity to show the effects of installing the package. I'm only talking about the context of the developer who is adding the new ebuild. So ABI_SLOT (or / SLOT) would be set automatically just once, in the process of committing the ebuild. No need to repeat the binary analysis - except if one source package has different ABI for different ARCHes. Fun! //Peter
