On 12/9/22 23:54, Lee Duncan wrote:
Thank you for your reply! I believe you are likely correct. I did more online OBS packaging guidelines research, and it looks like that is what is done.
But in my case, this library had an older version:
old: libopeniscsiusr.so.0.1.0 new: libopeniscsiusr.so.0.2.0
No interfaces went away, but new ones were added. FWIW.
So, bottom line, if I change this package name from libopeniscsiusr0_2_0 to libopeniscsiusr0, how will I handle the new version update, i.e. when libopeniscsiusr0_3_0 comes out? (If it ever does)
If the major version number remains 0, the ABI versions should be compatible with each other and no version bump should be necessary.
Also, if I change the name, won't I need an "obsoletes" clause in the updated SPEC file?
Normally, all reverse dependencies would have to be rebuilt in OBS. This way, the library dependencies are updated automatically. So there is no need to use Provides/Obsoletes. It's only important that the name of the -devel package remains unchanged but that's usually the case because it's normally without an ABI version as it should. Adrian