Hi! KDevPlatform has apparantly just been uploaded building the following binary packages:
kdevplatform - KDevelop platform for KDE4 kdevplatform-dbg - debugging symbols for the KDevelop platform kdevplatform-dev - development files for the KDevelop platform libsublime-dev - development files for the sublime user interface library libsublime1 - an user interface library where the first among others contain the following files as shared libraries: ./usr/lib/libkdevplatformtestshell.so.1.0.0 ./usr/lib/libkdevplatforminterfaces.so.1.0.0 ./usr/lib/libkdevplatformoutputview.so.1.0.0 ./usr/lib/libkdevplatformshell.so.1.0.0 ./usr/lib/libkdevplatformveritas.so.1.0.0 ./usr/lib/libkdevplatformvcs.so.1.0.0 ./usr/lib/libkdevplatformlanguage.so.1.0.0 ./usr/lib/libkdevplatformproject.so.1.0.0 ./usr/lib/libkdevplatformutil.so.1.0.0 and the kdevplatform-dev package offers headers and .so symlinks for these libraries. This is wrong according to how libraries are traditionally packaged in kde team, wrong according to how libraries are traditionally packaged in debian and wrong according to debian policy. Stuffing the libraries together in one package do probably make sense here, just like in the kdelibs5 and kdepimlibs5 packages, but naming the package without a version number is the major problem. If one day, any of the libkdevplatform* libraries changes ABI, the package name must change and the "kdevplatform" name can not be used for this. This also breaks it for future major versions of KDE, where the abi is actually changing. I know this is far in the future and that the Debian KDE team most probably is different then, but it does not give us the right to deliver a pile of crap on their tables when we have the possibility to avoid it. Oh. and policy section 8 if you want that. /Sune -- I cannot get access over the connection over a Internet address, how does it work? From ICQ you cannot boot the CPU for saving a tool.
Description: This is a digitally signed message part.