Re: lib/x86_64-linux-gnu/libKF5FileMetaData.so | lib/libKF5FileMetaData.3.dylib

2015-12-19 Thread David Faure
On Wednesday 16 December 2015 17:42:29 šumski wrote: > On Wednesday 16 of December 2015 09:08:03 David Faure wrote: > > Fixed, it was an oversight when converting the lib into a KF5 framework. > > But this is a BiC change... One that is generally allowed (not like removing a virtual method and

Re: lib/x86_64-linux-gnu/libKF5FileMetaData.so | lib/libKF5FileMetaData.3.dylib

2015-12-17 Thread šumski
On Thursday 17 of December 2015 12:51:42 René J. V. Bertin wrote: > šumski wrote: > >> Yes, bug fixes can do that ;) > > > > Yes, but frameworks are under BC guarantee. > > So how are bugs supposed to be fixed if they break ABI compatibility? Certainly not by breaking one of core policies. >

Re: lib/x86_64-linux-gnu/libKF5FileMetaData.so | lib/libKF5FileMetaData.3.dylib

2015-12-17 Thread René J . V . Bertin
šumski wrote: >> Yes, bug fixes can do that ;) > Yes, but frameworks are under BC guarantee. So how are bugs supposed to be fixed if they break ABI compatibility? If I'm not mistaken Linux will not check beyond shared library file names. If that's correct, the build system can install a

Re: lib/x86_64-linux-gnu/libKF5FileMetaData.so | lib/libKF5FileMetaData.3.dylib

2015-12-16 Thread René J . V . Bertin
šumski wrote: >> Fixed, it was an oversight when converting the lib into a KF5 framework. > > But this is a BiC change... Yes, bug fixes can do that ;) R ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org

Re: lib/x86_64-linux-gnu/libKF5FileMetaData.so | lib/libKF5FileMetaData.3.dylib

2015-12-16 Thread šumski
On Wednesday 16 of December 2015 09:08:03 David Faure wrote: > Fixed, it was an oversight when converting the lib into a KF5 framework. But this is a BiC change... Cheers, Hrvoje ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org

Re: lib/x86_64-linux-gnu/libKF5FileMetaData.so | lib/libKF5FileMetaData.3.dylib

2015-12-16 Thread David Faure
Fixed, it was an oversight when converting the lib into a KF5 framework. > On Tuesday December 15 2015 18:55:52 René J.V. Bertin wrote: > > for packaging purposes it would be preferable if all libraries (symlinks) > > that are recorded in dependents' dependency lists are of the form > >

Re: lib/x86_64-linux-gnu/libKF5FileMetaData.so | lib/libKF5FileMetaData.3.dylib

2015-12-16 Thread René J . V . Bertin
On Wednesday December 16 2015 09:08:03 David Faure wrote: > Fixed, it was an oversight when converting the lib into a KF5 framework. Hah, you're welcome O:-) I had already taken the liberty to apply it myself (setting SOVERSION to 5); good to know it'll be part of the next release. >

lib/x86_64-linux-gnu/libKF5FileMetaData.so | lib/libKF5FileMetaData.3.dylib

2015-12-15 Thread René J . V . Bertin
Out of curiosity: is it intended that KFileMetaData sets the library compatibility version to 3, leading to /opt/local/lib/x86_64-linux-gnu/libKF5FileMetaData.so /opt/local/lib/x86_64-linux-gnu/libKF5FileMetaData.so.3 /opt/local/lib/x86_64-linux-gnu/libKF5FileMetaData.so.5.17.0 and on OS X %>

Re: lib/x86_64-linux-gnu/libKF5FileMetaData.so | lib/libKF5FileMetaData.3.dylib

2015-12-15 Thread René J . V . Bertin
On Tuesday December 15 2015 18:55:52 René J.V. Bertin wrote: > for packaging purposes it would be preferable if all libraries (symlinks) > that are recorded in dependents' dependency lists are of the form > libKF5*.5.dylib or libKF5*.so.5 (KFileMetadata is the only deviant one). PS : KDE4's