Porting to frameworks 2: libkcompactdisc

Alexander Potashev aspotashev at gmail.com
Mon Sep 7 08:55:52 BST 2015


2015-09-04 14:59 GMT+03:00 Friedrich W. H. Kossebau <kossebau at kde.org>:
> Am Freitag, 4. September 2015, 02:28:49 schrieb Alexander Potashev:
>> I think the new fancy library naming scheme is
>> "libKF5Xxx.so.SOVERSION", regardless of it being part of KF5 or not.
>> Thus libKF5CompactDisc.so.5.
>
> If that really is the scheme (is that noted somewhere?), I would ask to
> reconsider it. For once, because it will result in clashes if a lib really
> becomes part of KF5 (and thus becomes part of other packages which might be
> installed together with a package where the lib was initially in, unless the
> lib is the only content of the package, so that can be completely replaced by
> the KF5 package)
>
> And also does it blur the hint by the name if something is part of KF5 or not.
> This lib may be using KF5, but it is not KF5. That namespace should be left to
> KF5 libs, like  libQt* is left to Qt libs.
>
> I would rather propose libkcompactdisc2.so.SOVERSION here, so namespacing by
> postfix number. There is also the pattern libkcompactdisc-qt5.so.SOVERSION,
> which strikes out the dep to qt5, but not my favourite due to that
> verboseness. :)

Hi Friedrich,

It won't clash when the library moves to KF5 if you bump the version
to the next KF5 version to be released (e.g. 5.15 at the moment). It's
even better to keep the same naming scheme when for the library when
it joins KF5 because dependent projects won't need adaptation to the
new library name.

And I guess library users won't care if the library is part of KF5 or not.

-- 
Alexander Potashev




More information about the kde-core-devel mailing list