Detailed symbols.map

[Christopher James Halse Rogers]

On Thu, Aug 27, 2015 at 1:30 PM, Daniel van Vugt 
<daniel.van.vugt at canonical.com> wrote:
> That's the problem. We don't have abi-check automated yet. Although 
> we don't have to limit ourselves to that.
> 
> What we do have is regular ABI breaks landing and nobody noticing. So 
> I audit the code manually and propose the missing breaks. Fortunately 
> the whole team is getting on board and noticing them more often, but 
> it's still not automated.

And why is this a problem? We run abi-check as a part of the release 
process, and the ABI breaks (by and large) haven't broken CI (or the 
branch wouldn't have landed).

It would be *preferable* to bump ABI along with the branch that breaks 
it, but what is the problem if it isn't?

We know a *good* solution - automating abi-check - is reasonably close 
to implementable and should be reasonably cheap to implement. Is the 
problem so urgent that we should spend effort on an inferior stop-gap?