Mark Walters <markwalters1009@gmail.com> writes: > The first is a concern that if we change the library functions we should > update the library version otherwise out of tree users won't know which > to call. This is not such a big deal. We can update the SONAME of the library so that old code will continute to dynamically link to the old version of the library. Nothing [1] will magically make the old code work with the new library if we change the API; that is just the way things go, occasionally APIs and/or ABIs change. [1] Well maybe symbol versioning. I don't fully understand that, but I suspect it is more trouble than it is worth.