No because alternatives and kde default components are different. Alternatives are system-wide, they require sudo (root privileges). Kde default components are per-user, they don't require any privileges.
In my opinion, the best ideal solution would be that alternatives could handle per-user configuration and don't require sudo, then kde default components could use the alternatives system. But that is tricky. You have to think about usercases in multi-user environments, how updates would affect per-user alternatives, etc. It would be great to have a specification, https://wiki.ubuntu.com/FeatureSpecifications , but so far no one has volunteered to even try to write it.
Anyway, if you think there is an easy solution, it is worth to try to detail it and write a specification. If you (or someone else) implement it, it would be certainly better than the current situation.
@Ian
No because alternatives and kde default components are different. Alternatives are system-wide, they require sudo (root privileges). Kde default components are per-user, they don't require any privileges.
In my opinion, the best ideal solution would be that alternatives could handle per-user configuration and don't require sudo, then kde default components could use the alternatives system. But that is tricky. You have to think about usercases in multi-user environments, how updates would affect per-user alternatives, etc. It would be great to have a specification, https:/ /wiki.ubuntu. com/FeatureSpec ifications , but so far no one has volunteered to even try to write it.
Anyway, if you think there is an easy solution, it is worth to try to detail it and write a specification. If you (or someone else) implement it, it would be certainly better than the current situation.