Why the llvm14 provide package libclang13-14.0.0?
Hello. When I maintain my dependencies repo in OBS, the package llvm on Leap is unresolvable because of "nothing provides libclang13 >= 14.0.0 needed by clang14-devel", which is really strange, because I think it should require libclang14, following the major version of llvm14. Then I found out the package llvm14 truly is providing libclang13-14.0.0. Is there a reason we need to keep using libclang13 or is this just a mistake?
On 4/7/22 14:11, Orville Q. Song wrote:
Hello.
When I maintain my dependencies repo in OBS, the package llvm on Leap is unresolvable because of "nothing provides libclang13 >= 14.0.0 needed by clang14-devel", which is really strange, because I think it should require libclang14, following the major version of llvm14.
The -devel project will always require which ever libs were built alongside it.
Then I found out the package llvm14 truly is providing libclang13-14.0.0. Is there a reason we need to keep using libclang13 or is this just a mistake?
Here objdump -x /usr/lib64/libclang.so.13 returns SONAME libclang.so.13 In the case of both our library naming and where we put the package we should follow whatever is listed as the soname in the binary. As long as everything in the clang14 version of libclang.so is binary compatible with whatever was previously released as libclang.so.13 they technically don't have to change the version number there. Its basically saying you don't need to rebuild your package that depends on libclang because the new library is compatible with the old one. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
participants (2)
-
Orville Q. Song -
Simon Lees