Patrick O'Callaghan wrote:
1) using "... update kde*" will also pull in any
dependencies that KDE
needs from updates-testing, so you don't need anything else.
Not necessarily, sometimes it misses some stuff.
2) not restricting yourself to kde* (and its dependencies) increases
risk of a flaky system because you're updating a bunch of stuff you
don't care about. It can then be hard to back out to *not* using
updates-testing for every future update.
But this is true.
I'd suggest using the kde-testing repository instead. It also gets builds
sooner than updates-testing.