On Fri, May 31, 2019 at 8:18 AM Darren Smith <[email protected]> wrote: > > Hi > > I've noticed that from libuv-1.10.2 to libuv-1.29.1 (just an arbitrary wide > range I selected), the shared library SONAME is libuv.so.1 and further, the > name of the shared library is always libuv.so.1.0.0 > > Naively I would expect the SONAME to increase over such a wide range of > versions; or even, assuming these versions are API compatible, I would have > expected the minor & patch version number to alter. > > Perhaps instead libuv project always sets the SONAME to 1.0? Or am I > missing a build option? Or are these version API compatible? > > Darren
See [0] for more discussion. To summarize: 1. libuv.so.1.0.0 is probably wrong - we should bump the second digit every release and the last digit every minor release 2. libuv.so.1 is right because libuv v1.x releases are all backwards compatible with previous releases (barring the occasional snafu that we then subsequently fix) If the first item is an issue for you, then please open an issue or a pull request. For context, [1] is what we use for making releases. Libuv supports three build systems (autotools, cmake and gyp) and with some it's probably harder to configure than with others. E.g., I don't believe gyp really lets you (which is okay, that's only for Node.js and they don't care about the SONAME.) Hope that helps! [0] https://github.com/libuv/libuv/issues/1745 [1] https://github.com/libuv/libuv-release-tool -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/libuv. To view this discussion on the web visit https://groups.google.com/d/msgid/libuv/CAHQurc_PPBpaY%3DRxhOYNMD8Kmd1jfvA4KSkFj43qFhX0nabZQA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
