Yes, of a sort. I still get lots of KDE packages updated only because of small changes in one component, although this is mitigated somewhat by my removing most of KDE by hand.
If I understand the updating process correctly, this is caused by the fact that KDE comes in a big fat source package, and a single update requires re-compiling everything else. So it's not something that can be solved at update (aptitude) level. AFAIK the only fix would be splitting the big KDE source package in several smaller source packages, a bit like gnome does. I'm not sure how realistic that is.
Yes, of a sort. I still get lots of KDE packages updated only because of small changes in one component, although this is mitigated somewhat by my removing most of KDE by hand.
If I understand the updating process correctly, this is caused by the fact that KDE comes in a big fat source package, and a single update requires re-compiling everything else. So it's not something that can be solved at update (aptitude) level. AFAIK the only fix would be splitting the big KDE source package in several smaller source packages, a bit like gnome does. I'm not sure how realistic that is.