> This could be easily fixed by passing a fixed SOVERSION argument to
> ecm_setup_version(). But which one should be used? Would it be correct to
> use 5 even if the library version is going to be YY.MM.DD ?
It should be 5 if there have been no ABI-breaking changes since 18.04 and 6
otherwise.
On venerdì 20 luglio 2018 21:53:12 CEST, Antonio Rojas wrote:
Hi,
In 18.08 baloo-widgets follows the KDE-Applications version
number. This has the side effect that the libKF5BalooWidgets
soversion has bumped from 5 to 18, and will presumably keep
getting bumped every year (regardless of API ch
Hi,
In 18.08 baloo-widgets follows the KDE-Applications version number. This
has the side effect that the libKF5BalooWidgets soversion has bumped from 5
to 18, and will presumably keep getting bumped every year (regardless of
API changes). This seems wrong to me. Looking at the source it seems
SVN commit 1520490 by aacid:
KDE Applications 18.08 Beta
CCMAIL: release-team@kde.org
M +0 -1 announcements/announce-applications-18.08-beta.php
M +5 -0 announcements/index.php
M +5 -0 index.php
A info/applications-18.07.80.php
A info/sourc
