[marble] [Bug 374208] New: libmarblewidget versioning

[RJVB]

https://bugs.kde.org/show_bug.cgi?id=374208

            Bug ID: 374208
           Summary: libmarblewidget versioning
           Product: marble
           Version: 2.1 (KDE Applications 16.12)
          Platform: Compiled Sources
                OS: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: NOR
         Component: general
          Assignee: marble-bugs at kde.org
          Reporter: rjvbertin at gmail.com
  Target Milestone: ---

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).

-- 
You are receiving this mail because:
You are the assignee for the bug.