Over the course of my time upgrading KDE, there's always an issue of packages being removed that needed to be reinstalled or packages being removed which becomes incompatible with an upgrade. So, I solicit an explanation from one of our enlightened gurus, TerryN. I hope to convey his explanation in the hope that or users would understand why things are in such a way. I don't know how else to work around the issue but I do remember that pinoc created a script that would detect the apps that would be removed upon an upgrade and reinstall those apps again. Perhaps that would be the solution.
Anyway, here's an excerpt from our correspondence:
Archie: How do I prevent other install packages from getting removed when I update a package? It is happening again. I just packaged kdelibs-4.9.3 and when I try to update 4.9.2, it wants to take out a whole bunch of 4.9.2s plus others. Is there a way to go around this and only get kdelibs-4.9.2 and kdelibs-devel-4.9.2 updated to 4.9.3?
TerryN: The packages get removed because the new package doesn't provide a library dependency that they NEED. This is usually because a library ABI version (called %major in the SPEC file) has changed. For example the old package has libfoo.so.8 and the new package has libfoo.so.9 but the dependent packages NEED libfoo.so.8. The upstream developers change the ABI version when they make a change which is NOT backward compatible (which means applications built against libfoo.so.8 will not work with libfoo.so.9). Therefore there is no choice but to rebuild the dependent packages against the new version of the library (or re-engineer KDE to make the libraries co-exist). They can still be the same 4.9.2 packages but they need to be rebuilt with kdelibs-devel-4.9.3 installed instead of kdelibs-devel-4.9.2.
So the short answer is NO. There isn't a way around this without significantly re-engineering KDE. Much easier to rebuild the dependent
Archie: It should be easy enough to get a list of dependents and up them a release number and updates should run OK. Am I correct in assuming that?
TerryN: I would think they will install OK but whether they will play nicely together or not is another matter. I've always had the impression that the KDE devs work on the assumption that the whole SC (or at the very least each module) is kept at the same revision level.
As I've mentioned on another thread, 4.9.3 and 4.9.4 will not be made available, and testing will resume on maybe 4.10 (Jan 23, 2013) and definitely 4.10.1 (Mar 5, 2013). Before this stage, I will contact pinoc, and if he willing to work together and improve his KDEupgrade script, this may solve KDE's big problem.
Once again, thank you, Terry for you valuable insight and explanation. It is much appreciated.
Peace and much respect,