Simon McVittie wrote: >On Fri, 07 Feb 2020 at 09:28:24 +0200, Wouter Verhelst wrote: >> Why not? This seems like the type of problem that SONAMEs are made for. >> What am I missing? > >SONAMEs are set by the upstream developer in their build system (building >the same source code produces the same SONAME), and are cross-distro >comparable/compatible. This makes them good for representing ABI breaks >that result from changes to the upstream source code (like deleting >a deprecated function or changing a struct's members), but bad for >representing ABI breaks that result from external factors like a toolchain >or compilation-option change. > >We didn't/couldn't change SONAMEs for the C++11 std::string transition >(g++ 5, "v5" suffix), which was a similar situation.
Nod, exactly. This involves tracking all the way up the library stack, which makes it hard. We *can* go the suffix route if preferred, but that's a *lot* of effort - see proposal A... -- Steve McIntyre, Cambridge, UK. st...@einval.com Armed with "Valor": "Centurion" represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud.