On Monday 05 August 2013 20:57:33 Chusslove Illich wrote: > My notion of source compatibility was that it builds and works, not only > that it builds :) Is there really a point of leaving in dummy methods just > so that the build can proceed, even if they do nothing? As I mentioned, my > intention was to commit everything necessary for the build to work, but I > plainly screwed up.
Do you plan to also port overnight for all the other software produced by KDE once people want to start to KF5? That's why the SC compatibility rule is important. They'll have to change their CMakeLists.txt already to get the thing to roll, if they have to also fix at the same time for the ThreadWeaver API changes, the ki18n API changes, the kdeui API changes, etc. They'll just give up and can't be blamed. That's why even a no-op which spawns a warning is better in that case, at least they can do the port gradually instead of a big bang of changes. Sometimes we can't manage to keep SC, we broke it at a few places already but that was necessary evil... so let's not add more when we can spare them. Regards. -- Kévin Ottens, http://ervin.ipsquad.net Sponsored by BlueSystems and KDAB to work on KDE Frameworks
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
