Bug 374208 - libmarblewidget versioning
Summary: libmarblewidget versioning
Status: RESOLVED WORKSFORME
Alias: None
Product: marble
Classification: Applications
Component: general (show other bugs)
Version: 2.1 (KDE Applications 16.12)
Platform: Compiled Sources All
: NOR minor
Target Milestone: ---
Assignee: marble-bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-27 12:09 UTC by RJVB
Modified: 2022-11-26 05:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RJVB 2016-12-27 12:09:45 UTC
For 2 iterations now I've noticed that the version in the library name changes without any apparent *backwards-incompatible* changes to the ABI (or indeed to the compatibility version on Mac):

With both .so.24->.so.25 (16.04->16.08) and .so.25->.so.26 (16.08->16.12) I could install a symlink making the new library available under the previous filename, and keep using it with digiKam without having to rebuild that (huge) bit of software.

Wouldn't it be more appropriate to use a composite versioning scheme, something like

libmarblewidget.so.2.6
libmarblewidget.so.2 -> libmarblewidget.so.2.6
libmarblewidget.so -> libmarblewidget.so.2

which would allow updating Marble without updating or rebuilding 3rd party software using libmarblewidget?

This would evidently require a bit more careful implementation/consideration of ABI changes. But a priori backwards compatibility should be the norm if Qt and KDE's approach of using d-pointers is followed (and it seems this is the case).
Comment 1 Justin Zobel 2022-10-27 02:48:29 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-11-11 05:20:01 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-11-26 05:17:36 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!