Closed acbits closed 2 years ago
it is a bug that will be fixed with 1.2.2
I am assuming that you would name the libmysofa.so version as 1.2.2 to match the tag?
SO version are usually unrelated to the package (or project) version. Here are some answer: https://stackoverflow.com/questions/7553184/how-to-do-versioning-of-shared-library
That been said, it can be an indication. (say if libmysofa 2.x is introduced breaking ABI with libmysofa.so.1)
True, but many packages follow a convention of stamping the release version onto the shared files. I think glibc does it that way as it is easier to track what release a library belongs to.
i think it's the other way round (or at least should be): many packages follow the convention of semantic versioning for the package version, even though strictly speaking it is only required of the soname version.
The tag is 1.2.1, but the libmysofa.so built is actually libmysofa.so.1.1.0, and the deb package built is also named libmysofa-1.1.0-Linux.deb.
Was that intentional naming or a bug?