On 2014/12/10 22:57, Lukas Tribus wrote: > I get your point, but I don't believe its always that simple. Should we really > exclusively care about users of the packaging systems provided by the OS, > nobody else?
The standard way to handle this for build-from-source is with pkg-config. I haven't looked at what changes have been made to .pc files but I'd hope that versions there are updated when there's an API change. > Having no idea what libssl/lilbcrypto release the application was build > against > is not very pleasant when you have to troubleshoot strange problems or crahes > and in the end the simple reason is that there is no ABI or even API > compatibility between the library the application was build against and the > library that is actually running. For shared library version numbers, you can expect OpenBSD code to follow the usual rules, major bump = incompatible change (function removed or parameters changed), minor bump = addition (code compiled against older minor versions works with a newer one; code compiled against newer minor version won't work against an older one).
